Bug 615600 - [abrt] crash in kdebase-runtime-4.4.5-1.fc13: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in kdebase-runtime-4.4.5-1.fc13: Process /usr/bin/nepomukservice...
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-runtime   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:860f47ae1b206b6627c12b1c343...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-17 11:09 UTC by Mircea Sava
Modified: 2011-03-18 16:30 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-03-18 16:30:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (1.79 KB, text/plain)
2010-07-17 11:09 UTC, Mircea Sava
no flags Details

Description Mircea Sava 2010-07-17 11:09:04 UTC
abrt 1.1.1 detected a crash.

architecture: i686
cmdline: /usr/bin/nepomukservicestub nepomukstorage
component: kdebase-runtime
executable: /usr/bin/nepomukservicestub
global_uuid: 860f47ae1b206b6627c12b1c343643f169fba7be
package: kdebase-runtime-4.4.5-1.fc13
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

BFD: Warning: /var/cache/abrt/ccpp-1279143955-1938/coredump is truncated: expected core file size >= 121036800, found: 73728.
warning: core file may not match specified executable file.
[New Thread 2194]
[New Thread 2196]
[New Thread 2285]
[New Thread 2291]
[New Thread 2185]
[New Thread 2192]
[New Thread 1938]
[New Thread 3059]
[New Thread 2195]
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/nepomukservicestub nepomukstorage'.
Program terminated with signal 6, Aborted.
#0  0x00a08416 in ?? ()

Thread 9 (Thread 2195):
Cannot access memory at address 0xb47fd040

Thread 8 (Thread 3059):
Cannot access memory at address 0xb1ff9040

Thread 7 (Thread 1938):
Cannot access memory at address 0xbf94d960

Thread 6 (Thread 2192):
Cannot access memory at address 0xb5bff040

Thread 5 (Thread 2185):
Cannot access memory at address 0xb67ff040

Thread 4 (Thread 2291):
Cannot access memory at address 0xb29fa040

Thread 3 (Thread 2285):
Cannot access memory at address 0xb33fb040

Thread 2 (Thread 2196):
Cannot access memory at address 0xb3dfc040

Thread 1 (Thread 2194):
Cannot access memory at address 0xb51fd674
From        To          Syms Read   Shared Object Library
0x003df830  0x003f73bf  Yes         /lib/ld-linux.so.2
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
eax            0x0	0
ecx            0x892	2194
edx            0x6	6
ebx            0x792	1938
esp            0xb51fd674	0xb51fd674
ebp            0xb51fd680	0xb51fd680
esi            0x0	0
edi            0x6baff4	7057396
eip            0xa08416	0xa08416
eflags         0x202	[ IF ]
cs             0x73	115
ss             0x7b	123
ds             0x7b	123
es             0x7b	123
fs             0x0	0
gs             0x33	51
No function contains program counter for selected frame.

Comment 1 Mircea Sava 2010-07-17 11:09:07 UTC
Created attachment 432572 [details]
File: backtrace

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