Bug 726269 - [abrt] xulrunner-1.9.2.18-2.el6_1: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
Summary: [abrt] xulrunner-1.9.2.18-2.el6_1: Process /usr/lib64/xulrunner-1.9.2/plugin-...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xulrunner
Version: 6.0
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Christopher Aillon
QA Contact: Desktop QE
URL:
Whiteboard: abrt_hash:b830eba6d750b88fd2104983989...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-28 01:37 UTC by Red Hat Case Diagnostics
Modified: 2018-11-14 11:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-05 22:37:02 UTC
Target Upstream Version:


Attachments (Terms of Use)
File: backtrace (1.45 KB, text/plain)
2011-07-28 01:38 UTC, Red Hat Case Diagnostics
no flags Details

Description Red Hat Case Diagnostics 2011-07-28 01:37:52 UTC
This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline: /usr/lib64/xulrunner-1.9.2/plugin-container /home/rciloci/.mozilla/plugins/libflashplayer.so 22200 plugin
component: xulrunner
executable: /usr/lib64/xulrunner-1.9.2/plugin-container
kernel: 2.6.32-131.6.1.el6.x86_64
package: xulrunner-1.9.2.18-2.el6_1
reason: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Server release 6.1 (Santiago)
reproduce: 1. I don't know.
2.
3.

time: 1311816699
uid: 500
backtrace: BFD: Warning: /var/spool/abrt/ccpp-1311816699-22244/coredump is truncated: expected core file size >= 57290752, found: 10444800.
warning: core file may not match specified executable file.
[New Thread 22245]
[New Thread 22244]
Cannot access memory at address 0x7f2d09efc6f0

Thread 2 (Thread 22244):
#0  0x00000030db80803d in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fffa5250fc0

Thread 1 (Thread 22245):
#0  0x00007f2cf8475d00 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7f2d09ec7c58
Cannot access memory at address 0x7f2d09efc6f0
No symbol table is loaded.  Use the "file" command.
No symbol table is loaded.  Use the "file" command.
rax            0x7f2cf8475d00	139831120715008
rbx            0xa0	160
rcx            0x200	512
rdx            0x7f2d0457dff0	139831323123696
rsi            0x0	0
rdi            0x7f2d040b7470	139831318115440
rbp            0x30dba18340	0x30dba18340
rsp            0x7f2d09ec7c58	0x7f2d09ec7c58
r8             0x1	1
r9             0x56e5	22245
r10            0x1	1
r11            0x3a98	15000
r12            0x7f2d09ec8a10	139831416752656
r13            0x0	0
r14            0x0	0
r15            0x30dba182a0	209843225248
rip            0x7f2cf8475d00	0x7f2cf8475d00
eflags         0x10206	[ PF IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
gs             0x0	0
No function contains program counter for selected frame.

Comment 2 Red Hat Case Diagnostics 2011-07-28 01:38:31 UTC
Created attachment 515614 [details]
File: backtrace

Comment 5 Jeremy West 2011-10-05 22:37:02 UTC
Closing this bug, since the associated customer case has closed.  Please feel free to re-open this if new information becomes available.


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