GNOME Bugzilla – Bug 549808
crash in Anjuta IDE: Trying to debug Debian b...
Last modified: 2009-03-09 11:51:18 UTC
Version: 2.4.2 What were you doing when the application crashed? Trying to debug Debian bug #495144. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495144 anjuta 2:2.4.2-1 Commands to reproduce: $ anjuta -n create a new generic C++ project using all the defaults, choosing an empty directory for the project let the project initialise and then use Build Project from the Build Menu. Run Execute Program from the Build Menu, leaving "in terminal" set. Anjuta hangs. Killing the anjuta-launcher process restores anjuta functionality *unless* the project is modified to not use the terminal plugin. With the terminal disabled, anjuta raises a temporary terminal to execute the program and then hangs. Killing the anjuta-launcher process now causes this crash and this bug-buddy output. $ ps waux | grep anjuta neil 22827 4.5 1.0 321272 42576 pts/1 Sl+ 11:52 0:00 anjuta foobar_cpp.anjuta neil 22844 0.0 0.0 15104 724 pts/10 Ss+ 11:52 0:00 anjuta_launcher /opt/debian/src/rc/anjuta-test/src/foobar_cpp neil@holly:~$ kill 22844 No particular output on the terminal that started anjuta (although that might be because bug-buddy has captured it). Crash is reproducible on loading the anjuta project file from this new project (as the project has the terminal disabled) and trying to execute the program in a terminal window. anjuta-launcher itself works fine in a different terminal: $ anjuta_launcher /opt/debian/src/rc/anjuta-test/src/foobar_cpp EXECUTING: /opt/debian/src/rc/anjuta-test/src/foobar_cpp ---------------------------------------------- Hello world! ---------------------------------------------- Program exited successfully with errcode (0) Press the Enter key to close this terminal ... $ echo $? 0 Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Fri Aug 8 13:17:41 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 329117696 vsize: 329117696 resident: 43831296 share: 16039936 rss: 43831296 rss_rlim: 18446744073709551615 CPU usage: start_time: 1220007121 rtime: 94 utime: 76 stime: 18 cutime:3 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/anjuta' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f79e412c770 (LWP 22827)] [New Thread 0x40e5d950 (LWP 22838)] 0x00007f79defdc5ff in waitpid () from /lib/libpthread.so.0
+ Trace 205843
Thread 1 (Thread 0x7f79e412c770 (LWP 22827))
----------- .xsession-errors (428 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... --------------------------------------------------
Installing anjuta-dbg gives this backtrace (via bug-buddy after killing anjuta-launcher with anjuta frozen and the terminal plugin disabled in preferences). Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Fri Aug 8 13:17:41 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 329097216 vsize: 329097216 resident: 43724800 share: 16023552 rss: 43724800 rss_rlim: 18446744073709551615 CPU usage: start_time: 1220007810 rtime: 76 utime: 64 stime: 12 cutime:2 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/anjuta' [Thread debugging using libthread_db enabled] [New Thread 0x7f107e9bf770 (LWP 23234)] [New Thread 0x417e6950 (LWP 23244)] 0x00007f107986f5ff in waitpid () from /lib/libpthread.so.0
+ Trace 205844
Thread 1 (Thread 0x7f107e9bf770 (LWP 23234))
----------- .xsession-errors (1120 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... --------------------------------------------------
Thanks for reporting. We have some similar reports and the cause of the problem was a buggy version of libvte (the gnome terminal library). Would be nice if you could check this with a more recent (or older) version of libvte. Thanks!
libvte9 is only available at v 1:0.16.14-3 in Debian - older versions are not installable (SONAME transitions). Can you give me the bugzilla bug numbers for these other reports? I think I might be experiencing the same problem with Geany, it also embeds a terminal within and IDE/editor type app. Ubuntu Intrepid is using libvte9 1:0.17.2-0ubuntu2 - I'll see if I can find someone to test Anjuta in Ubuntu.
OK, what I managed to do is download the source that Ubuntu use (1:0.17.2-0.1) and build it as a Debian package, replacing my 1:0.16.14-3 packages with the new ones: Setting up libvte-common (1:0.17.2-0.1) ... Setting up libvte9 (1:0.17.2-0.1) ... Setting up python-vte (1:0.17.2-0.1) ... Setting up libvte-dev (1:0.17.2-0.1) ... The minor problem that I had been experiencing in Geany has gone away. The crash in Anjuta has not. Same method, same result: *** glibc detected *** anjuta: corrupted double-linked list: 0x0000000003812f30 *** The best way to get a backtrace is to disable Terminal in the installed plugin preferences, execute the program - anjuta waits for anjuta-launcher. Kill anjuta-launcher and you get the backtrace. (Kill anjuta and there is no backtrace.) Other methods cause anjuta to hang but not produce a backtrace.
There is a problem with the libvte 0.16.14 or higher. The version 0.16.13 is working. The corresponding bug is 538344, I have written a patch but it has not been committed yet. Then, there is probably a problem if you don't use the terminal plugin. I haven't tried recently so I will check this.
I have looked at this bug and there several possibilities now: The "run program" menu item has been partialy rewritten in Anjuta 2.5.x. Could you try the latest version of Anjuta from SVN ? Or at least Anjuta 2.5.90 (or 2.5.91) ? The patch that I have sent for vte, has just been committed so you can recompile the latest version of vte (revision 2090) and try again. I have just committed some changes in Anjuta to use gnome-terminal instead of vte if the terminal plugin is missing. So if you use the latest revision of Anjuta (revision 4204), you can remove the anjuta-terminal.plugin file in /usr/local/lib/anjuta/, gnome-terminal will be used and I hope it will work.
Neil, do you have any chance to test with the changes Sebastien mentioned in comment #6?
Sorry for not getting to look at this sooner - been rather busy with Lenny and other packages. I've just tried to reproduce this bug with the current binary package in Debian unstable, 2:2.24.2-1, and the bug is unreproducible. Everything works as expected and anjuta continues to operate. I've tried with and without terminal and it works fine from the changed menu in 2.24. I'm following up to the Debian bug with the same result but I think this bug can be closed. (I'm unable to close the bug myself in bugzilla.)
Hey Neil :) Thanks for your feedback! I am happy to close this bug as dup of 538344. *** This bug has been marked as a duplicate of 538344 ***