Bug 537581 – crash in Anjuta IDE: Creating a new makefile ...

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 537581 - crash in Anjuta IDE: Creating a new makefile ...


Summary:	crash in Anjuta IDE: Creating a new makefile ...


Status:	RESOLVED DUPLICATE of bug 543637

Product:	anjuta
Classification:	Applications
Component:	plugins: symbol-db
Version:	2.5.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-10 13:14 UTC by duni.bg
Modified:	2008-08-15 23:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description duni.bg 2008-06-10 13:14:01 UTC

Version: 2.5.0

What were you doing when the application crashed?
Creating a new makefile project.


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.2 2008-05-28 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.3-18.fc9.i686 #1 SMP Tue May 13 05:38:53 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10499901
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 59437056 vsize: 59437056 resident: 23969792 share: 15470592 rss: 23969792 rss_rlim: 4294967295
CPU usage: start_time: 1213103497 rtime: 150 utime: 134 stime: 16 cutime:0 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 0xb8016730 (LWP 12327)]
0x00110416 in __kernel_vsyscall ()

+ Trace 200027

Thread 1 (Thread 0xb8016730 (LWP 12327))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 symbol_db_engine_add_new_files
at symbol-db-engine.c line 2937
#10 project_root_added
at plugin.c line 984
#11 value_added_cb
at anjuta-plugin.c line 371
#12 anjuta_cclosure_marshal_VOID__STRING_BOXED
at anjuta-marshal.c line 314
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 ??
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#17 anjuta_shell_add_value
at anjuta-shell.c line 409
#18 on_profile_scoped
at plugin.c line 1296
#19 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /lib/libgobject-2.0.so.0
#21 ??
from /lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#23 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#24 anjuta_profile_manager_load_profile
at anjuta-profile-manager.c line 409
#25 anjuta_new
at anjuta.c line 484
#26 main
at main.c line 386



----------- .xsession-errors ---------------------
(anjuta:12168): Gdl-WARNING **: master 0x92eee60: unable to add object 0xab5fe88[AnjutaSymbolBrowser] to the hash.  There already is an item with that name (0xa3ffe28).
** Message: no rows
(anjuta:12168): libgnomevfs-CRITICAL **: gnome_vfs_uri_new_private: assertion `text_uri != NULL' failed
(anjuta:12168): libgnomevfs-CRITICAL **: gnome_vfs_uri_new_private: assertion `text_uri != NULL' failed
(anjuta:12168): libgnomevfs-CRITICAL **: gnome_vfs_format_uri_for_display_internal: assertion `uri != NULL' failed
(anjuta:12168): libanjuta-CRITICAL **: anjuta_util_str_middle_truncate: assertion `string != NULL' failed
** Message: Spawning script
(anjuta:12327): libanjuta-WARNING **: Failed to synchronize plugins profile 'project': File not found
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------

Comment 1 Massimo Cora' 2008-08-15 23:31:42 UTC

Patches for this bug will be on trunk soon.
Thanks for reporting this bug,
Massimo

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