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 627288 - Segmentation fault on fedora 13
Segmentation fault on fedora 13
Status: RESOLVED INCOMPLETE
Product: anjuta
Classification: Applications
Component: plugins: symbol-db
git master
Other Linux
: Normal critical
: ---
Assigned To: Massimo Cora'
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-18 17:50 UTC by Maxim Ermilov
Modified: 2010-10-26 23:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Maxim Ermilov 2010-08-18 17:50:33 UTC 
It happen after creating new project.
Affected version: 2.30.0.1/ TRUNK

(anjuta:15365): GLib-GObject-CRITICAL **: g_value_get_int: assertion `G_VALUE_HOLDS_INT (value)' failed

(anjuta:15365): libanjuta-symbol-db-WARNING **: No version of db detected. This can produce many errors.

(anjuta:15365): libanjuta-symbol-db-WARNING **: Error while trying to open a shared memory file. Besure to have /dev/shm mounted with tmpfs

(anjuta:15365): libanjuta-symbol-db-WARNING **: Error while trying to open a shared memory file. Besure to have /dev/shm mounted with tmpfs
Segmentation fault (core dumped)


Backtrace:
(gdb) backtrace

+ Trace 223288

  • #0 fwrite
    from /lib64/libc.so.6
  • #1 sdb_engine_ctags_output_thread
    at symbol-db-engine-core.c line 1010
  • #2 g_thread_pool_thread_proxy
    at gthreadpool.c line 314
  • #3 g_thread_create_proxy
    at gthread.c line 1897
  • #4 start_thread
    from /lib64/libpthread.so.0
  • #5 clone
    from /lib64/libc.so.6 

shm_open (shared_temp_file, O_CREAT|O_RDWR, S_IRUSR|S_IWUSR)) return Permission denided.
Comment 1 Maxim Ermilov 2010-08-18 20:18:38 UTC 
backtrace  after shm_open

+ Trace 223291

  • #0 sdb_engine_scan_files_1
    at symbol-db-engine-core.c line 1390
  • #1 symbol_db_engine_add_new_files_full
    at symbol-db-engine-core.c line 3066
  • #2 sdb_system_do_engine_scan
    at symbol-db-system.c line 516
  • #3 symbol_db_system_parse_aborted_package
    at symbol-db-system.c line 830
  • #4 do_import_system_sources_after_abort
    at plugin.c line 1169
  • #5 do_import_system_sources
    at plugin.c line 1304
  • #6 on_session_load
    at plugin.c line 1532
  • #7 g_closure_invoke
    at gclosure.c line 766
  • #8 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #9 g_signal_emit_valist
    at gsignal.c line 2983
  • #10 g_signal_emit_by_name
    at gsignal.c line 3077
  • #11 anjuta_shell_session_load
    at anjuta-shell.c line 929
  • #12 on_profile_scoped
    at anjuta.c line 168
  • #13 g_closure_invoke
    at gclosure.c line 766
  • #14 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #15 g_signal_emit_valist
    at gsignal.c line 2983
  • #16 g_signal_emit_by_name
    at gsignal.c line 3077
  • #17 anjuta_profile_manager_load_profile
    at anjuta-profile-manager.c line 463
  • #18 anjuta_new
    at anjuta.c line 421
  • #19 main
    at main.c line 255 

(gdb) inspect priv->shared_mem_fd
$2 = -1
Comment 2 Massimo Cora' 2010-08-19 22:17:20 UTC 
hmm do you have /dev/shm/ activated?
Can you write there?
Comment 3 Massimo Cora' 2010-08-19 22:19:28 UTC 
there's a flag
  --with-symbol-db-shm=DIR
                          Where shared memory is placed

that you can use to specify the shm destination.
But if you don't have permission there's some misconfiguration with fc13 maybe.
Comment 4 Felipe Besoaín Pino 2010-10-26 23:13:06 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!