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 597267 - crash in Anjuta IDE: Creating a generic proje...
crash in Anjuta IDE: Creating a generic proje...
Status: RESOLVED DUPLICATE of bug 597275
Product: anjuta
Classification: Applications
Component: unknown
1.2.1
Other All
: Normal critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-04 09:48 UTC by Luca Bruno
Modified: 2009-10-04 12:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Luca Bruno 2009-10-04 09:48:40 UTC
Version: 2.28.0.0

What were you doing when the application crashed?
Creating a generic project


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-09-27 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-1-amd64 #1 SMP Sat Aug 15 18:09:19 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10603901
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaAzul
Icon Theme: Mist
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 286470144 vsize: 286470144 resident: 23949312 share: 15679488 rss: 23949312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254649682 rtime: 162 utime: 104 stime: 58 cutime:28 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fced5679950 (LWP 15178)]
[New Thread 0x7fced6e07950 (LWP 15175)]
0x00007fcee155128f in __libc_waitpid (pid=15198, stat_loc=0x7fffade97ab0, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7fcee338b790 (LWP 15174))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 symbol_db_engine_add_new_project
    from /usr/lib/anjuta/libanjuta-symbol-db.so
  • #6 ??
    from /usr/lib/anjuta/libanjuta-symbol-db.so
  • #7 ??
    from /usr/lib/libanjuta.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/anjuta/libanjuta-project-manager.so
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libanjuta.so.0
  • #18 ??
    from /usr/lib/anjuta/libanjuta-project-manager.so
  • #19 ??
    from /usr/lib/anjuta/libanjuta-loader.so
  • #20 ??
    from /usr/lib/anjuta/libanjuta-project-wizard.so
  • #21 ??
    from /usr/lib/anjuta/libanjuta-project-wizard.so
  • #22 ??
    from /usr/lib/anjuta/libanjuta-project-wizard.so
  • #23 ??
    from /usr/lib/anjuta/libanjuta-project-wizard.so
  • #24 ??
    from /usr/lib/anjuta/libanjuta-project-wizard.so
  • #25 ??
    from /usr/lib/anjuta/libanjuta-project-wizard.so
  • #26 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libanjuta.so.0
  • #31 ??
    from /lib/libglib-2.0.so.0
  • #32 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #33 ??
    from /lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #35 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 main
Current language:  auto; currently c
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (21 sec old) ---------------------
(xchat-gnome:2146): Gtk-WARNING **: Ran out of links
(xchat-gnome:2146): Gtk-WARNING **: Ran out of links
(xchat-gnome:2146): Gtk-WARNING **: Ran out of links
(xchat-gnome:2146): Gtk-WARNING **: Ran out of links
(xchat-gnome:2146): Gtk-WARNING **: Ran out of links
(xchat-gnome:2146): Gtk-WARNING **: Ran out of links
(xchat-gnome:2146): Gtk-WARNING **: Ran out of links
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3a000e6 specified for 0x3a00082 ().
--------------------------------------------------
Comment 1 Luca Bruno 2009-10-04 12:01:02 UTC

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