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 533078 - crash in Anjuta IDE: Lancement de l'opération...
crash in Anjuta IDE: Lancement de l'opération...
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-14 09:22 UTC by Houssame.Yahiaoui
Modified: 2008-05-14 10:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Houssame.Yahiaoui 2008-05-14 09:22:25 UTC 
Version: 2.4.0

What were you doing when the application crashed?
Lancement de l'opération de Nettoyage du Projet à partir de l'IDE (projet avec Makefile personnalisé)


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 36519936 vsize: 36519936 resident: 24932352 share: 14667776 rss: 24932352 rss_rlim: 4294967295
CPU usage: start_time: 1210681790 rtime: 6647 utime: 5333 stime: 1314 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 0xb6eff720 (LWP 22458)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197689

Thread 1 (Thread 0xb6eff720 (LWP 22458))

  • #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 (6 sec old) ---------------------
OPENING /home/houssame/MyWork/MySources/SABIS/policyparser/policyParser.tab.c as C language file
OPENING /home/houssame/MyWork/MySources/SABIS/policyparser/policyParser.tab.h as C++ language file
OPENING /home/houssame/MyWork/MySources/SABIS/policyparser/policyParser.yy.c as C language file
OPENING /home/houssame/MyWork/MySources/SABIS/scenarioparser/scenarioParser.tab.c as C language file
OPENING /home/houssame/MyWork/MySources/SABIS/scenarioparser/scenarioParser.tab.h as C++ language file
OPENING /home/houssame/MyWork/MySources/SABIS/scenarioparser/scenarioParser.yy.c as C language file
OPENING /home/houssame/MyWork/MySources/SABIS/cSessionManager.h as C++ language file
OPENING /home/houssame/MyWork/MySources/SABIS/fullmesh_n.cc as C++ language file
OPENING /home/houssame/MyWork/MySources/SABIS/cSessionManager.h as C++ language file
OPENING /home/houssame/MyWork/MySources/SABIS/cSessi
(anjuta:22458): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed
(anjuta:22458): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(anjuta:22458): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
--------------------------------------------------
Comment 1 Johannes Schmid 2008-05-14 10:19:45 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 ***