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 664835 - [abrt] tracker-0.12.7-1.fc16: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
[abrt] tracker-0.12.7-1.fc16: Process /usr/libexec/tracker-miner-fs was kille...
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Miners
0.12.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2011-11-25 18:57 UTC by Deji Akingunola
Modified: 2011-12-06 16:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Deji Akingunola 2011-11-25 18:57:10 UTC 
Fedora Bug: https://bugzilla.redhat.com/show_bug.cgi?id=756860

crash_function: tracker_sparql_buffer_update_array_cb
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.1.1-2.fc16.x86_64
pid:            19363
reason:         Process /usr/libexec/tracker-miner-fs was killed by signal 11
(SIGSEGV)

Backtrace:
warning: core file may not match specified executable file.
[New LWP 19363]
[New LWP 19367]
[New LWP 19366]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/tracker-miner-fs'.
Program terminated with signal 11, Segmentation fault.

+ Trace 229134

Thread 1 (Thread 0x7f8774c99840 (LWP 19363))

  • #0 tracker_sparql_buffer_update_array_cb
    at tracker-sparql-buffer.c line 303
  • #1 g_simple_async_result_complete
    at gsimpleasyncresult.c line 749
  • #2 tracker_sparql_backend_real_update_array_async_co
    at /home/juerg/Code/tracker/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 120
  • #3 g_simple_async_result_complete
    at gsimpleasyncresult.c line 749
  • #4 tracker_bus_connection_real_update_array_async_co
    at /home/juerg/Code/tracker/tracker/src/libtracker-bus/tracker-bus.vala line 258
  • #5 __lambda4_
    at /home/juerg/Code/tracker/tracker/src/libtracker-bus/tracker-bus.vala line 219
  • #6 ___lambda4__gasync_ready_callback
    at /home/juerg/Code/tracker/tracker/src/libtracker-bus/tracker-bus.vala line 216
  • #7 g_simple_async_result_complete
    at gsimpleasyncresult.c line 749
  • #8 _vala_g_async_ready_callback
    at tracker-bus.c line 793
  • #9 g_simple_async_result_complete
    at gsimpleasyncresult.c line 749
  • #10 complete_in_idle_cb
    at gsimpleasyncresult.c line 761
  • #11 g_main_dispatch
    at gmain.c line 2425
  • #12 g_main_context_dispatch
    at gmain.c line 2995
  • #13 g_main_context_iterate
    at gmain.c line 3073
  • #14 g_main_loop_run
    at gmain.c line 3281
  • #15 main
    at tracker-main.c line 863 






Comment 1


Martyn Russell





          2011-12-06 16:05:14 UTC
        



This bug was fixed by these commits:

  ea964e65bddecbe4c388a111138ea3c8253daf3e
  8750c7142ecfe1d9d2f25b4ac44c3fff046223d9

These fixes are found in release 0.12.8.