Ubuntu
anjuta package

segfault in symbol_db_engine_file_exists()

Bug #438792 reported by Mirco Müller on 2009-09-29

This bug report is a duplicate of: Bug #442725: anjuta segmentation fault with new project. Edit Remove

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	anjuta (Ubuntu)	Fix Released	High	Unassigned

Bug Description

Binary package hint: anjuta

Trying to start anjuta causes a segfault in symbol_db_engine_file_exists() from /usr/lib/anjuta/libanjuta-symbol-db.so

Running anjuta under gdb and getting a backtrace I was presented with this...

#0 0x00007fffea5c05d5 in symbol_db_engine_file_exists () from /usr/lib/anjuta/libanjuta-symbol-db.so
#1 0x00007fffea5c0d2e in symbol_db_engine_update_files_symbols () from /usr/lib/anjuta/libanjuta-symbol-db.so
#2 0x00007fffea5c13b8 in symbol_db_engine_update_project_symbols () from /usr/lib/anjuta/libanjuta-symbol-db.so
#3 0x00007fffea5a816b in ?? () from /usr/lib/anjuta/libanjuta-symbol-db.so
#4 0x00007ffff4ce6e53 in ?? () from /usr/lib/libanjuta.so.0
#5 0x00007ffff541660e in IA__g_closure_invoke (closure=0xed1eb0, return_value=0x0, n_param_values=3, param_values=0x22dc370, invocation_hint=0x7fffffffda50) at /build/buildd/glib2.0-2.22.0/gobject/gclosure.c:767
#6 0x00007ffff542b933 in signal_emit_unlocked_R (node=0x6b80e0, detail=<value optimized out>, instance=<value optimized out>, emission_return=<value optimized out>, instance_and_params=<value optimized out>)
at /build/buildd/glib2.0-2.22.0/gobject/gsignal.c:3247
#7 0x00007ffff542cce9 in IA__g_signal_emit_valist (instance=0x6c0000, signal_id=<value optimized out>, detail=0, var_args=0x7fffffffdc50) at /build/buildd/glib2.0-2.22.0/gobject/gsignal.c:2980
#8 0x00007ffff542d054 in IA__g_signal_emit_by_name (instance=0x6c0000, detailed_signal=0x40bfe7 "value_added") at /build/buildd/glib2.0-2.22.0/gobject/gsignal.c:3074
#9 0x00007fffebf68bc4 in ?? () from /usr/lib/anjuta/libanjuta-project-manager.so
#10 0x00007ffff541660e in IA__g_closure_invoke (closure=0x99ab40, return_value=0x0, n_param_values=2, param_values=0x21f74f0, invocation_hint=0x7fffffffdf20) at /build/buildd/glib2.0-2.22.0/gobject/gclosure.c:767
#11 0x00007ffff542b933 in signal_emit_unlocked_R (node=0x6de130, detail=<value optimized out>, instance=<value optimized out>, emission_return=<value optimized out>, instance_and_params=<value optimized out>)
at /build/buildd/glib2.0-2.22.0/gobject/gsignal.c:3247
#12 0x00007ffff542cce9 in IA__g_signal_emit_valist (instance=0x730cc0, signal_id=<value optimized out>, detail=0, var_args=0x7fffffffe120) at /build/buildd/glib2.0-2.22.0/gobject/gsignal.c:2980
#13 0x00007ffff542d054 in IA__g_signal_emit_by_name (instance=0x730cc0, detailed_signal=0x7ffff4d1bf5d "profile-scoped") at /build/buildd/glib2.0-2.22.0/gobject/gsignal.c:3074
#14 0x00007ffff4cefe7f in ?? () from /usr/lib/libanjuta.so.0
#15 0x0000000000407f3f in ?? ()
#16 0x000000000040b789 in ?? ()
#17 0x00007ffff454babd in __libc_start_main () from /lib/libc.so.6
#18 0x0000000000406ff9 in ?? ()
#19 0x00007fffffffe488 in ?? ()
#20 0x000000000000001c in ?? ()
#21 0x0000000000000001 in ?? ()
#22 0x00007fffffffe7bf in ?? ()
#23 0x0000000000000000 in ?? ()

Related branches

lp:~ubuntu-desktop/anjuta/ubuntu

lp:ubuntu/lucid/anjuta

Mirco Müller (macslow) on 2009-09-29

Changed in anjuta (Ubuntu):
importance:	Undecided → High

Revision history for this message

Paulo Assis (pj-assis) wrote on 2009-09-29:

Download full text (5.4 KiB)

Hi,
i have exactly the same problem since the last anjuta update in karmic.
Running under valgrind:

==5514== Memcheck, a memory error detector.
==5514== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al.
==5514== Using LibVEX rev 1884, a library for dynamic binary translation.
==5514== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP.
==5514== Using valgrind-3.4.1-Debian, a dynamic binary instrumentation framework.
==5514== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al.
==5514== For more details, rerun with: -v
==5514==

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: anjuta.toolbar.visible
--5514-- WARNING: unhandled syscall: 332
--5514-- You may be able to write your own handler.
--5514-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--5514-- Nevertheless we consider this a bug. Please report
--5514-- it at http://valgrind.org/support/bug_reports.html.

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: margin.linenumber.visible

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: margin.marker.visible

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: margin.fold.visible

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: view.indentation.guides

Hi,
i have exactly the same problem since the last anjuta update in karmic.
Running under valgrind:

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: anjuta.toolbar.visible
--5514-- WARNING: unhandled syscall: 332
--5514-- You may be able to write your own handler.
--5514-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--5514-- Nevertheless we consider this a bug.  Please report
--5514-- it at http://valgrind.org/support/bug_reports.html.

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: margin.linenumber.visible

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: margin.marker.visible

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: margin.fold.visible

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: view.indentation.guides

(anjuta:5514): libanjuta-WARNING **: Invalid gconf type for key: view.whitespace
==5523== 
==5523== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 437 from 2)
==5523== malloc/free: in use at exit: 8,047,184 bytes in 54,886 blocks.
==5523== malloc/free: 890,424 allocs, 835,538 frees, 87,408,019 bytes allocated.
==5523== For counts of detected errors, rerun with: -v
==5523== searching for pointers to 54,886 not-freed blocks.
==5523== checked 8,050,768 bytes.
==5523== 
==5523== LEAK SUMMARY:
==5523==    definitely lost: 23,032 bytes in 320 blocks.
==5523==      possibly lost: 4,580,916 bytes in 3,548 blocks.
==5523==    still reachable: 3,443,236 bytes in 51,018 blocks.
==5523==         suppressed: 0 bytes in 0 blocks.
==5523== Rerun with --leak-check=full to see details of leaked memory.
==5514== Invalid read of size 4
==5514==    at 0x7AD6E09: symbol_db_engine_file_exists (in /usr/lib/anjuta/libanjuta-symbol-db.so)
==5514==    by 0x7AD75BB: symbol_db_engine_update_files_symbols (in /usr/lib/anjuta/libanjuta-symbol-db.so)
==5514==    by 0x7AD7CE9: symbol_db_engine_update_project_symbols (in /usr/lib/anjuta/libanjuta-symbol-db.so)
==5514==    by 0x7ABBD0D: (within /usr/lib/anjuta/libanjuta-symbol-db.so)
==5514==    by 0x4AA3773: (within /usr/lib/libanjuta.so.0.0.0)
==5514==    by 0x4A98A6E: anjuta_cclosure_marshal_VOID__STRING_BOXED (in /usr/lib/libanjuta.so.0.0.0)
==5514==    by 0x497A091: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.2200.0)
==5514==    by 0x498F6F7: (within /usr/lib/libgobject-2.0.so.0.2200.0)
==5514==    by 0x4990A7C: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.2200.0)
==5514==    by 0x4990D91: g_signal_emit_by_name (in /usr/lib/libgobject-2.0.so.0.2200.0)
==5514==    by 0x4A99E9D: anjuta_shell_add_value (in /usr/lib/libanjuta.so.0.0.0)
==5514==    by 0x70A0EC4: (within /usr/lib/anjuta/libanjuta-project-manager.so)
==5514==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==5514== 
==5514== Process terminating with default action of signal 11 (SIGSEGV)
==5514==  Access not within mapped region at address 0x0
==5514==    at 0x7AD6E09: symbol_db_engine_file_exists (in /usr/lib/anjuta/libanjuta-symbol-db.so)
==5514==    by 0x7AD75BB: symbol_db_engine_update_files_symbols (in /usr/lib/anjuta/libanjuta-symbol-db.so)
==5514==    by 0x7AD7CE9: symbol_db_engine_update_project_symbols (in /usr/lib/anjuta/libanjuta-symbol-db.so)
==5514==    by 0x7ABBD0D: (within /usr/lib/anjuta/libanjuta-symbol-db.so)
==5514==    by 0x4AA3773: (within /usr/lib/libanjuta.so.0.0.0)
==5514==    by 0x4A98A6E: anjuta_cclosure_marshal_VOID__STRING_BOXED (in /usr/lib/libanjuta.so.0.0.0)
==5514==    by 0x497A091: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.2200.0)
==5514==    by 0x498F6F7: (within /usr/lib/libgobject-2.0.so.0.2200.0)
==5514==    by 0x4990A7C: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.2200.0)
==5514==    by 0x4990D91: g_signal_emit_by_name (in /usr/lib/libgobject-2.0.so.0.2200.0)
==5514==    by 0x4A99E9D: anjuta_shell_add_value (in /usr/lib/libanjuta.so.0.0.0)
==5514==    by 0x70A0EC4: (within /usr/lib/anjuta/libanjuta-project-manager.so)
==5514==  If you believe this happened as a result of a stack overflow in your
==5514==  program's main thread (unlikely but possible), you can try to increase
==5514==  the size of the main thread stack using the --main-stacksize= flag.
==5514==  The main thread stack size used in this run was 8388608.
==5514== 
==5514== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 437 from 2)
==5514== malloc/free: in use at exit: 8,541,953 bytes in 59,090 blocks.
==5514== malloc/free: 936,189 allocs, 877,099 frees, 91,044,656 bytes allocated.
==5514== For counts of detected errors, rerun with: -v
==5514== searching for pointers to 59,090 not-freed blocks.
==5514== checked 16,835,644 bytes.
==5514== 
==5514== LEAK SUMMARY:
==5514==    definitely lost: 28,606 bytes in 618 blocks.
==5514==      possibly lost: 4,919,126 bytes in 4,184 blocks.
==5514==    still reachable: 3,594,221 bytes in 54,288 blocks.
==5514==         suppressed: 0 bytes in 0 blocks.
==5514== Rerun with --leak-check=full to see details of leaked memory.

So it seems there is a access attempt at address 0x00 (a NULL pointer maybe).

Best regards,
Paulo

Revision history for this message

stop (whoopwhoop) wrote on 2009-10-02:

Happens here as well on 64 bit karmic.

Revision history for this message

Mirco Müller (macslow) wrote on 2009-10-08:

The "corrected debdiff" attached to LP: #442725 fixes this crasher for me.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2009-10-08:

This bug was fixed in the package anjuta - 2:2.28.0.0-0ubuntu2

---------------
anjuta (2:2.28.0.0-0ubuntu2) karmic; urgency=low

  * debian/patches/fix-symbol_db-segfault.patch:
    - Fix segfault on project creation (LP: #442725, LP: #438792) (bgo 597113)
      (patch from upstream git)

-- Hugues Fournier <email address hidden> Wed, 07 Oct 2009 20:39:48 +0200

Changed in anjuta (Ubuntu):
status:	New → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #442725 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuanjuta package

segfault in symbol_db_engine_file_exists()

Bug Description

Related branches

Other bug subscribers

Remote bug watches

Ubuntu
anjuta package