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 539521 - crash in Meld Diff Viewer: I had started the applic...
crash in Meld Diff Viewer: I had started the applic...
Status: VERIFIED DUPLICATE of bug 508758
Product: meld
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Stephen Kennedy
Stephen Kennedy
Depends on:
Blocks:
 
 
Reported: 2008-06-21 21:11 UTC by olivier.jolly
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description olivier.jolly 2008-06-21 21:11:52 UTC 
What were you doing when the application crashed?
I had started the application with 2 directories on command line


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.16-2-k7 #1 Fri Aug 18 19:48:42 UTC 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Sandy

Memory status: size: 34177024 vsize: 34177024 resident: 21413888 share: 12763136 rss: 21413888 rss_rlim: 4294967295
CPU usage: start_time: 1214082655 rtime: 74 utime: 51 stime: 23 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/meld'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xa7d4b6b0 (LWP 5673)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 201039

Thread 1 (Thread 0xa7d4b6b0 (LWP 5673))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 g_markup_escape_text
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 g_value_transform
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_set_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_widget_set_tooltip_text
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 _gtk_marshal_BOOLEAN__OBJECT_STRING_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #0 __kernel_vsyscall 






Comment 1


Kai Willadsen





          2008-09-25 22:56:43 UTC
        



Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

In addition, a Python stack trace would be very helpful, if you know how to obtain one. Thanks.






Comment 2


André Klapper





          2008-11-01 23:04:22 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 508758 ***