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 534183 - crash in Anjuta IDE: Trying to compile the pr...
crash in Anjuta IDE: Trying to compile the pr...
Status: RESOLVED DUPLICATE of bug 467698
Product: anjuta
Classification: Applications
Component: unknown
2.4.x
Other All
: High critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-21 12:57 UTC by mjdom
Modified: 2008-05-21 13:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description mjdom 2008-05-21 12:57:16 UTC 
Version: 2.4.1

What were you doing when the application crashed?
Trying to compile the project. Shift+F11.


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

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 40476672 vsize: 40476672 resident: 27430912 share: 14123008 rss: 27430912 rss_rlim: 4294967295
CPU usage: start_time: 1211374435 rtime: 188 utime: 178 stime: 10 cutime:0 cstime: 0 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 0xb6e76720 (LWP 9586)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198298

Thread 1 (Thread 0xb6e76720 (LWP 9586))

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


----------- .xsession-errors ---------------------
    Vera: 
    Verilog: 
    Vim: 
OPENING /home/matteus/Projects/monark_fcm/trunk/src/exercise_mode_window_ctrl.c as C language file
OPENING /home/matteus/Projects/monark_fcm/trunk/src/manual_window_ctrl.c as C language file
OPENING /home/matteus/Projects/monark_fcm/trunk/src/exercise_mode_window_ctrl.c as C language file
OPENING /home/matteus/Projects/monark_fcm/trunk/src/SC/card.h as C++ language file
OPENING /home/matteus/Projects/monark_fcm/trunk/src/connection/monark_connect.h as C++ language file
OPENING /home/matteus/Projects/monark_fcm/trunk/src/connection/monark_connect.c as C language file
OPENING /home/mat
(anjuta:9586): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed
(anjuta:9586): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(anjuta:9586): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
--------------------------------------------------
Comment 1 Johannes Schmid 2008-05-21 13:19:27 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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