Bug 593281 - [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 ...
Status: CLOSED DUPLICATE of bug 550334
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:cf186419dcda7f7f09d59d3e956...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-18 12:24 UTC by Robbin
Modified: 2010-05-25 09:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-25 09:06:19 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (14.09 KB, text/plain)
2010-05-18 12:24 UTC, Robbin
no flags Details

Description Robbin 2010-05-18 12:24:08 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gdb ../arch/x86_64-unknown-linux/bin/64/liquidatord
component: gdb
crash_function: raise
executable: /usr/bin/gdb
global_uuid: cf186419dcda7f7f09d59d3e95605b1bd204f956
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
set target-async 1
set pagination off
set non-stop on
r myparams
main thread does exit (other threads still alive)
(gdb) thread apply all bt
../../gdb/thread.c:581: internal-error: is_thread_state: Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

Comment 1 Robbin 2010-05-18 12:24:11 UTC
Created attachment 414833 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:06:19 UTC

*** This bug has been marked as a duplicate of bug 550334 ***

Comment 3 Karel Klíč 2010-05-25 09:06:19 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #550334.

Sorry for the inconvenience.

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