Bug 711000 - [abrt] prelink-0.4.4-1.el6: Process /usr/sbin/prelink was killed by signal 6 (SIGABRT)
Summary: [abrt] prelink-0.4.4-1.el6: Process /usr/sbin/prelink was killed by signal 6 ...
Keywords:
Status: CLOSED DUPLICATE of bug 788238
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: prelink
Version: 6.0
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jakub Jelinek
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard: abrt_hash:014a98e627a4ede57163e5055a6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-06 07:21 UTC by Red Hat Case Diagnostics
Modified: 2018-11-14 12:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-12 12:50:05 UTC
Target Upstream Version:


Attachments (Terms of Use)
File: backtrace (1.56 KB, text/plain)
2011-06-06 07:21 UTC, Red Hat Case Diagnostics
no flags Details
File: backtrace (1.55 KB, text/plain)
2011-06-27 15:49 UTC, Red Hat Case Diagnostics
no flags Details

Description Red Hat Case Diagnostics 2011-06-06 07:21:22 UTC
This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline: /usr/sbin/prelink -av -mR -f
comment: don't know, it is an automatic cron job. 
component: prelink
executable: /usr/sbin/prelink
kernel: 2.6.32-131.0.15.el6.x86_64
package: prelink-0.4.4-1.el6
reason: Process /usr/sbin/prelink was killed by signal 6 (SIGABRT)
release: Red Hat Enterprise Linux Server release 6.1 (Santiago)
reproduce: 1.it is a cron job, from the system. no idea
2.
3.

time: 1307344778
uid: 0
backtrace: [New Thread 5856]
Core was generated by `/usr/sbin/prelink -av -mR -f'.
Program terminated with signal 6, Aborted.
#0  0x000000000043c63b in ?? ()

Thread 1 (Thread 5856):
#0  0x000000000043c63b in ?? ()
No symbol table info available.
#1  0x0000000000455995 in ?? ()
No symbol table info available.
#2  0x0000000000402003 in ?? ()
No symbol table info available.
#3  0x000000000040f232 in ?? ()
No symbol table info available.
#4  0x000000000044e6cb in ?? ()
No symbol table info available.
#5  0x0000000000400349 in ?? ()
No symbol table info available.
#6  0x00007fffa0834f98 in ?? ()
No symbol table info available.
#7  0x0000000000000000 in ?? ()
No symbol table info available.
No shared libraries loaded at this time.
No symbol table is loaded.  Use the "file" command.
No symbol table is loaded.  Use the "file" command.
rax            0x0	0
rbx            0x7fffa07c95f0	140735885907440
rcx            0xffffffffffffffff	-1
rdx            0x6	6
rsi            0x16e0	5856
rdi            0x16e0	5856
rbp            0x7fffa0834de0	0x7fffa0834de0
rsp            0x7fffa07c94b8	0x7fffa07c94b8
r8             0x8	8
r9             0xffffffff	4294967295
r10            0x8	8
r11            0x202	514
r12            0x63ce5	408805
r13            0x7fffa0834d60	140735886347616
r14            0x7fffa07eeff8	140735886061560
r15            0xe29	3625
rip            0x43c63b	0x43c63b
eflags         0x202	[ IF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x63	99
gs             0x0	0
No function contains program counter for selected frame.

Comment 2 Red Hat Case Diagnostics 2011-06-06 07:21:57 UTC
Created attachment 503160 [details]
File: backtrace

Comment 6 Red Hat Case Diagnostics 2011-06-27 15:49:50 UTC
Created attachment 510115 [details]
File: backtrace

Comment 8 RHEL Program Management 2011-07-06 01:14:37 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.


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