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 517518 - crash in Anjuta IDE: when i was trying to und...
crash in Anjuta IDE: when i was trying to und...
Status: RESOLVED DUPLICATE of bug 467698
Product: anjuta
Classification: Applications
Component: unknown
2.2.x
Other All
: High critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-19 19:31 UTC by Sebastian Mach
Modified: 2008-02-19 20:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Sebastian Mach 2008-02-19 19:31:24 UTC
Version: 2.2.3

What were you doing when the application crashed?
when i was trying to undock the 'documents'-dock, an empty dock with no content at all (empty window, with the document title bar showing [sorry, i don't remember exactly] probably the default title, plus '#33' ).  

the documents-dock remained in the main-window. then i pressed the x-icon to close that window, et voila, unfortunately it crashed. the other anjuta-instance i had running with another project did not crash.

reproduction of that crash not succeeded, the next time it went fine.

greets,
Sebastian Mach
http://greenhybrid.net | seb(at)greenhybrid.net


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-486 #1 Sun Feb 10 19:36:16 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: Neu

Memory status: size: 92975104 vsize: 92975104 resident: 42909696 share: 15331328 rss: 42909696 rss_rlim: 4294967295
CPU usage: start_time: 1203440655 rtime: 21016 utime: 19321 stime: 1695 cutime:9640 cstime: 837 timeout: 0 it_real_value: 0 frequency: 100

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

(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 0xb6f416b0 (LWP 3249)]
[New Thread 0xb4edeb90 (LWP 10129)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6f416b0 (LWP 3249))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
OggS-SEEK: at 78400 want 520 got 0 (diff-requested -77880)
(anjuta:3249): libanjuta-WARNING **: Failed to synchronize plugins profile 'project': Datei nicht gefunden
(anjuta:3249): libanjuta-WARNING **: Failed to synchronize plugins profile 'project': Datei nicht gefunden
(anjuta:3249): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed
(anjuta:3249): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(anjuta:3249): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
warning: .dynamic section for "/lib/libsepol.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Johannes Schmid 2008-02-19 19:43:23 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.

It's very difficult to reproduce this but we hope it will be fixed in gtk+ soon!

*** This bug has been marked as a duplicate of 467698 ***
Comment 2 Sebastian Mach 2008-02-19 20:27:01 UTC
Thank *you*! Looking forward to see the fixes then.