Bug 590183 - [abrt] crash in gdb-7.0.1-45.fc12: raise: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gdb-7.0.1-45.fc12: raise: Process /usr/bin/gdb was killed by ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c21cdf8f329306f633f35d3454e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-07 23:11 UTC by Philippe Waroquiers
Modified: 2010-06-01 15:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-01 15:32:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (10.68 KB, text/plain)
2010-05-07 23:11 UTC, Philippe Waroquiers
no flags Details

Description Philippe Waroquiers 2010-05-07 23:11:30 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/gdb --annotate=3 /usr/lib/firefox-3.5/firefox
component: gdb
crash_function: raise
executable: /usr/bin/gdb
global_uuid: c21cdf8f329306f633f35d3454e158e3e7929644
kernel: 2.6.32.11-99.fc12.i686.PAE
package: gdb-7.0.1-45.fc12
rating: 4
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
I am busy integrating a gdbserver stub inside valgrind.
I was busy debugging firefox running under valgrind using gdb and the gdbserver integrated in valgrind.
When I quitted firefox, the connection between gdb and gdbserver was thus lost.
It seems that this then gives problems to gdb.

Comment 1 Philippe Waroquiers 2010-05-07 23:11:32 UTC
Created attachment 412462 [details]
File: backtrace

Comment 2 Jan Kratochvil 2010-06-01 15:32:30 UTC
While thanks for the bugreport these threading issues should be fixed in general in gdb-7.1 which is in F-13.
If you find it as a problem please upgrade to the stable F-13 distro.


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