Bug 625570 - [abrt] gdb-7.1-32.fc13: OP_IMREG: Process /usr/bin/gdb was killed by signal 4 (SIGILL)
Summary: [abrt] gdb-7.1-32.fc13: OP_IMREG: Process /usr/bin/gdb was killed by signal 4...
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb   
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:04edc4a0ab415dfb91f1a539ab5...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-19 20:29 UTC by Leif H.
Modified: 2010-08-19 20:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-19 20:49:37 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (13.93 KB, text/plain)
2010-08-19 20:29 UTC, Leif H. 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Leif H. 2010-08-19 20:29:44 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /usr/bin/eu-unstrip' -ex 'core-file /var/spool/abrt/ccpp-1282248996-2724/coredump' -ex 'thread apply all backtrace 2048 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info registers' -ex disassemble
component: gdb
crash_function: OP_IMREG
executable: /usr/bin/gdb
kernel: 2.6.33.6-147.2.4.fc13.i686
package: gdb-7.1-32.fc13
rating: 4
reason: Process /usr/bin/gdb was killed by signal 4 (SIGILL)
release: Fedora release 13 (Goddard)
time: 1282249028
uid: 500

How to reproduce
-----
1.Running Yum Extender
2.after some 30 seconds ... BANG
3.Started ABRT to report BUG, now a BANG in GDB
Comment 1 Leif H. 2010-08-19 20:29:46 UTC 
Created an attachment (id=439783)
File: backtrace
Comment 2 Jan Kratochvil 2010-08-19 20:49:37 UTC 
There is a bogus jump.
Just it is not reproducible for me on:
"\377\320\000\000Ue3\b\002\000\000\000\330P\276\000\035W "
->
   0x8048464 <buf>:	call   *%eax
   0x8048466 <buf+2>:	add    %al,(%eax)
   0x8048468 <buf+4>:	push   %ebp
   0x8048469 <buf+5>:	xor    %gs:(%eax),%ecx
   0x804846c <buf+8>:	add    (%eax),%al
   0x804846e <buf+10>:	add    %al,(%eax)
   0x8048470 <buf+12>:	fcoms  -0x42(%eax)
   0x8048473 <buf+15>:	add    %bl,0x1002057

Either attach the core file (for gdb, not that other crashed app) or I cannot fix it.  Thanks.
Note You need to log in before you can comment on or make changes to this bug.