Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 596143 - [abrt] crash in kdebase-workspace-4.4.2-5.fc12: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in kdebase-workspace-4.4.2-5.fc12: Process /usr/bin/plasma-deskt...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9dd88d1bc5783f0a45a7c21b313...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-26 12:03 UTC by Daya Shanker Prasad
Modified: 2010-07-13 06:40 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-13 06:40:10 UTC


Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-26 12:03 UTC, Daya Shanker Prasad
no flags Details

Description Daya Shanker Prasad 2010-05-26 12:03:32 UTC
abrt 1.0.9 detected a crash.

architecture: i686
cmdline: plasma-desktop --nocrashhandler
component: kdebase-workspace
executable: /usr/bin/plasma-desktop
global_uuid: 9dd88d1bc5783f0a45a7c21b313611d8521a1d39
kernel: 2.6.32.11-99.fc12.i686.PAE
package: kdebase-workspace-4.4.2-5.fc12
rating: 4
reason: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

backtrace
-----
BFD: Warning: /var/cache/abrt/ccpp-1274692998-7401/coredump is truncated: expected core file size >= 230187008, found: 3198976.
[New Thread 7420]
Core was generated by `plasma-desktop --nocrashhandler'.
Program terminated with signal 11, Segmentation fault.
#0  __kernel_vsyscall () at arch/x86/vdso/vdso32/sysenter.S:49
49		pop %ebp

Thread 2 (Thread 7420):
Cannot access memory at address 0xaa78bc3c

Thread 1 (Thread 7401):
Cannot access memory at address 0xbfff6bbc
From        To          Syms Read   Shared Object Library
0x00784830  0x0079bd0f  Yes (*)     /lib/ld-linux.so.2
(*): Shared library is missing debugging information.
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
eax            0x0	0
ecx            0x1ce9	7401
edx            0xb	11
ebx            0x1ce9	7401
esp            0xbfff6bb0	0xbfff6bb0
ebp            0xbfff6bc8	0xbfff6bc8
esi            0xb	11
edi            0xbc0ff4	12324852
eip            0x26b424	0x26b424 <__kernel_vsyscall+16>
eflags         0x202	[ IF ]
cs             0x73	115
ss             0x7b	123
ds             0x7b	123
es             0x7b	123
fs             0x0	0
gs             0x33	51
Dump of assembler code for function __kernel_vsyscall:
0x0026b414 <__kernel_vsyscall+0>:	push   %ecx
0x0026b415 <__kernel_vsyscall+1>:	push   %edx
0x0026b416 <__kernel_vsyscall+2>:	push   %ebp
0x0026b417 <__kernel_vsyscall+3>:	mov    %esp,%ebp
0x0026b419 <__kernel_vsyscall+5>:	sysenter 
0x0026b41b <__kernel_vsyscall+7>:	nop
0x0026b41c <__kernel_vsyscall+8>:	nop
0x0026b41d <__kernel_vsyscall+9>:	nop
0x0026b41e <__kernel_vsyscall+10>:	nop
0x0026b41f <__kernel_vsyscall+11>:	nop
0x0026b420 <__kernel_vsyscall+12>:	nop
0x0026b421 <__kernel_vsyscall+13>:	nop
0x0026b422 <__kernel_vsyscall+14>:	jmp    0x26b417 <__kernel_vsyscall+3>
0x0026b424 <__kernel_vsyscall+16>:	pop    %ebp
0x0026b425 <__kernel_vsyscall+17>:	pop    %edx
0x0026b426 <__kernel_vsyscall+18>:	pop    %ecx
0x0026b427 <__kernel_vsyscall+19>:	ret    
End of assembler dump.

Comment 1 Daya Shanker Prasad 2010-05-26 12:03:35 UTC
Created attachment 416783 [details]
File: backtrace

Comment 2 Radek Novacek 2010-07-13 06:40:10 UTC
This backtrace seems not useful at all. Please update abrt and KDE to most recent versions and try to reproduce this bug. If the problem reoccurs reopen this bug or open new bug. Thank you.


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