After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 69715 - autotranslating a new file hangs gtranslator
autotranslating a new file hangs gtranslator
Status: VERIFIED INCOMPLETE
Product: gtranslator
Classification: Other
Component: Autotranslation
HEAD
Other Linux
: Normal normal
: 0.40
Assigned To: Fatih Demir
Fatih Demir
Depends on:
Blocks:
 
 
Reported: 2002-01-25 23:53 UTC by Roy-Magne Mo
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Roy-Magne Mo 2002-01-25 23:53:10 UTC
Trying to autotranslate with gtranslator -a nn.po where nn.po is a new file
without the header filled out, segfaults gtranslator. 

gtranslator tries to create a dialog box, but seems to crash in the attempt.

Program received signal SIGSEGV, Segmentation fault.

Thread 1024 (LWP 17768)

  • #0 chunk_free
    at malloc.c line 3242
  • #1 __libc_free
    at malloc.c line 3154
  • #2 g_free
    from /usr/lib/libglib-1.2.so.0
  • #3 gtranslator_learn_buffer_free_hash_entry
    at learn.c line 202
  • #4 g_hash_table_foreach
    from /usr/lib/libglib-1.2.so.0
  • #5 gtranslator_learn_shutdown
    at learn.c line 642
  • #6 main
    at main.c line 406
  • #7 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129

Comment 1 Fatih Demir 2002-02-01 18:15:20 UTC
Yes, this is similar to another bug report which I did receive some
time ago.

I couldn't find a good way to do this fastly honestly...
Comment 2 Fatih Demir 2002-02-15 17:20:29 UTC
Could you please attach the test case for this problem to here?
I will then look why this does that.. the other bug I was talking
about is half-wise solved...
Comment 3 Ross Golder 2003-06-08 15:46:35 UTC
I believe this is currently fixed in CVS HEAD. Please close this bug.
Comment 4 Fatih Demir 2003-06-09 07:06:58 UTC
It's fixed, I just tried it :-)