Bug 638154 – crash in Anjuta IDE: just pressed the toggle ...

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 638154 - crash in Anjuta IDE: just pressed the toggle ...


Summary:	crash in Anjuta IDE: just pressed the toggle ...


Status:	RESOLVED DUPLICATE of bug 633018

Product:	anjuta
Classification:	Applications
Component:	unknown
Version:	2.32.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Anjuta maintainers
QA Contact:	Anjuta maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-12-28 03:41 UTC by alex bodnaru
Modified:	2010-12-28 08:51 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description alex bodnaru 2010-12-28 03:41:25 UTC

Version: 2.32.0.0

What were you doing when the application crashed?
just pressed the toggle messages button after i closed all the messages lists.


Distribution: Debian squeeze/sid
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-5-686 #1 SMP Fri Dec 10 16:12:40 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 1831391232 vsize: 1831391232 resident: 390635520 share: 11644928 rss: 390635520 rss_rlim: 18446744073709551615
CPU usage: start_time: 1292316484 rtime: 325848 utime: 304629 stime: 21219 cutime:38867 cstime: 8200 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x510c9b70 (LWP 4917)]
[New Thread 0xad998b70 (LWP 3806)]
0xb7863424 in __kernel_vsyscall ()

+ Trace 225287

Thread 1 (Thread 0xb696ea50 (LWP 3792))

#0 __kernel_vsyscall
#1 waitpid
at ../sysdeps/unix/syscall-template.S line 82
#2 ??
from /lib/libglib-2.0.so.0
#3 ??
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 message_view_set_flags
from /usr/lib/anjuta/libanjuta-message-view.so
#7 ??
from /usr/lib/anjuta/libanjuta-message-view.so
#8 g_param_spec_set_qdata
from /usr/lib/libgobject-2.0.so.0
#9 ??
#10 g_boxed_free
from /usr/lib/libgobject-2.0.so.0
#11 ??
#12 g_signal_has_handler_pending
from /usr/lib/libgobject-2.0.so.0
#13 ??
#14 g_signal_lookup
from /usr/lib/libgobject-2.0.so.0
#15 ??
#16 ??
from /usr/lib/libgobject-2.0.so.0
#17 gtk_toggle_button_toggled
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_param_spec_set_qdata
from /usr/lib/libgobject-2.0.so.0
#20 ??
#21 ??
from /usr/lib/libgobject-2.0.so.0
#22 g_boxed_free
from /usr/lib/libgobject-2.0.so.0
#23 ??
#24 ??
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_lookup
from /usr/lib/libgobject-2.0.so.0
#26 ??
#27 ??
from /usr/lib/libgobject-2.0.so.0
#28 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 g_param_spec_set_qdata
from /usr/lib/libgobject-2.0.so.0
#31 ??
#32 ??
from /usr/lib/libgobject-2.0.so.0
#33 g_boxed_free
from /usr/lib/libgobject-2.0.so.0
#34 ??
#35 ??
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_lookup
from /usr/lib/libgobject-2.0.so.0
#37 ??
#38 ??
from /usr/lib/libgobject-2.0.so.0
#39 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/libgobject-2.0.so.0
#43 g_boxed_free
from /usr/lib/libgobject-2.0.so.0
#44 ??
#45 ??
from /usr/lib/libgobject-2.0.so.0
#46 ??
from /usr/lib/libgobject-2.0.so.0
#47 ??
from /usr/lib/libgobject-2.0.so.0
#48 ??
from /usr/lib/libgtk-x11-2.0.so.0
#49 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#50 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#51 ??
from /usr/lib/libgdk-x11-2.0.so.0
#52 g_key_file_get_double_list
from /lib/libglib-2.0.so.0
#53 ??
#54 g_source_set_can_recurse
from /lib/libglib-2.0.so.0
#55 ??
#56 g_main_loop_quit
from /lib/libglib-2.0.so.0
#57 ??
#58 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#59 ??
#60 __libc_start_main
at libc-start.c line 228
#61 ??

A debugging session is active.

	Inferior 1 [process 3792] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libgthread-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/libglib-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgmodule-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/libdbus-1.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libpixman-1.so.0" is not at the expected address (wrong library or version mismatch?)
Error while mapping shared library sections:
/usr/lib/libxcb-render-util.so.0: No such file or directory.
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2010-12-28 03:53:00 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 Johannes Schmid 2010-12-28 08:51:08 UTC


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