Bug 882709 - [abrt] tracker-0.14.4-1.fc18: strlen: Process /usr/libexec/tracker-store was killed by signal 11 (SIGSEGV)
Summary: [abrt] tracker-0.14.4-1.fc18: strlen: Process /usr/libexec/tracker-store was ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: tracker
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:da37117d2f3fe0b09e376063f79...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-02 20:20 UTC by Jan Teichmann
Modified: 2013-01-10 09:18 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-10 09:18:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (22.43 KB, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: cgroup (126 bytes, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: core_backtrace (1.17 KB, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: dso_list (3.32 KB, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: environ (1.35 KB, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: maps (16.59 KB, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: open_fds (1.20 KB, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: proc_pid_status (922 bytes, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details
File: var_log_messages (314 bytes, text/plain)
2012-12-02 20:20 UTC, Jan Teichmann
no flags Details

Description Jan Teichmann 2012-12-02 20:20:01 UTC
Version-Release number of selected component:
tracker-0.14.4-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-store
crash_function: strlen
executable:     /usr/libexec/tracker-store
kernel:         3.6.7-5.fc18.x86_64
remote_result:  754708
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 strlen at ../sysdeps/x86_64/strlen.S:31
 #1 g_strdup at gstrfuncs.c:363
 #2 g_error_copy at gerror.c:503
 #3 _g_error_copy0 at /home/martyn/Source/tracker/src/tracker-store/tracker-store.vala:170
 #4 tracker_store_sparql_update_co at /home/martyn/Source/tracker/src/tracker-store/tracker-store.vala:369
 #5 tracker_store_task_finish_cb at /home/martyn/Source/tracker/src/tracker-store/tracker-store.vala:193
 #6 __lambda1_ at /home/martyn/Source/tracker/src/tracker-store/tracker-store.vala:246
 #7 ___lambda1__gsource_func at tracker-store.c:1356
 #12 tracker_main_main at /home/martyn/Source/tracker/src/tracker-store/tracker-main.vala:306

Potential duplicate: bug 754708

Comment 1 Jan Teichmann 2012-12-02 20:20:05 UTC
Created attachment 656218 [details]
File: backtrace

Comment 2 Jan Teichmann 2012-12-02 20:20:07 UTC
Created attachment 656219 [details]
File: cgroup

Comment 3 Jan Teichmann 2012-12-02 20:20:10 UTC
Created attachment 656220 [details]
File: core_backtrace

Comment 4 Jan Teichmann 2012-12-02 20:20:12 UTC
Created attachment 656221 [details]
File: dso_list

Comment 5 Jan Teichmann 2012-12-02 20:20:14 UTC
Created attachment 656222 [details]
File: environ

Comment 6 Jan Teichmann 2012-12-02 20:20:17 UTC
Created attachment 656223 [details]
File: limits

Comment 7 Jan Teichmann 2012-12-02 20:20:19 UTC
Created attachment 656224 [details]
File: maps

Comment 8 Jan Teichmann 2012-12-02 20:20:21 UTC
Created attachment 656225 [details]
File: open_fds

Comment 9 Jan Teichmann 2012-12-02 20:20:24 UTC
Created attachment 656226 [details]
File: proc_pid_status

Comment 10 Jan Teichmann 2012-12-02 20:20:27 UTC
Created attachment 656227 [details]
File: var_log_messages

Comment 11 Jan Teichmann 2013-01-10 09:18:11 UTC
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors.
I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.


Note You need to log in before you can comment on or make changes to this bug.