GNOME Bugzilla – Bug 486119
crash in Anjuta IDE: Trying to compile some c...
Last modified: 2008-03-07 13:16:17 UTC
What were you doing when the application crashed? Trying to compile some code Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 443281408 vsize: 443281408 resident: 83820544 share: 68890624 rss: 83820544 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192129331 rtime: 704 utime: 569 stime: 135 cutime:602 cstime: 317 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/anjuta' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912679493248 (LWP 8405)] (no debugging symbols found) 0x00002aaab031c945 in waitpid () from /lib64/libpthread.so.0
+ Trace 169804
Thread 1 (Thread 46912679493248 (LWP 8405))
----------- .xsession-errors (7 sec old) --------------------- Pascal: Perl: PHP: Python: Ruby: Scheme: Sh: SML: SQL: Tcl: Vera: Verilog: Vim: OPENING /home/schaiba/Projects/kr.1.13.1.c as C language file OPENING /home/schaiba/Projects/kr.1.13.1.c as C language file --------------------------------------------------
*** Bug 486127 has been marked as a duplicate of this bug. ***
Hmm, the backtrace looks rather strange because it does not list one single function call from the anjuta codebase.
Might be a duplicate of bug #467698!
Can you still reproduce this? And does it happen every time?
I don't use linux anymore for development, nor do I use anjuta. Sorry I can't be of more help to you.