Red Hat Bugzilla – Bug 625570
[abrt] gdb-7.1-32.fc13: OP_IMREG: Process /usr/bin/gdb was killed by signal 4 (SIGILL)
Last modified: 2010-08-19 16:49:37 EDT
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
Created an attachment (id=439783) File: backtrace
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.