Bug 621355 – [abrt] crash in gdb-7.0.1-49.fc12: raise: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)

Bug 621355 - [abrt] crash in gdb-7.0.1-49.fc12: raise: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)

Summary:	[abrt] crash in gdb-7.0.1-49.fc12: raise: Process /usr/bin/gdb was killed by ...

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	gdb (Show other bugs)
Sub Component:
Version:	12
Hardware:	i686 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jan Kratochvil
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:	abrt_hash:2b19bca032f013685aaff511f96...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-04 16:13 EDT by Philippe Waroquiers
Modified:	2010-08-05 15:14 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-08-05 15:07:52 EDT
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 (10.99 KB, text/plain) 2010-08-04 16:13 EDT, Philippe Waroquiers	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Philippe Waroquiers 2010-08-04 16:13:56 EDT

abrt 1.1.1 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: 2b19bca032f013685aaff511f969a50771a0f997
kernel: 2.6.32.16-150.fc12.i686.PAE
package: gdb-7.0.1-49.fc12
rating: 4
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
I was busy debugging firefox through a gdbserver that I am busy integrating in valgrind.
When I exited the firefox process running under valgrind, gdb sees that the connection
is lost (the debugging is started using   target remote | vgdb
when vgdb is a relay application with valgrind.

gdb reports that the msg 'Remote connection closed'
and then reported it aborted.

Comment 1 Philippe Waroquiers 2010-08-04 16:13:59 EDT

Created attachment 436653 [details]
File: backtrace

Comment 2 Philippe Waroquiers 2010-08-05 15:07:52 EDT

Problem does not happen anymore with gdb 7.2 SVN.

So, I guess it can be closed

Comment 3 Jan Kratochvil 2010-08-05 15:14:32 EDT

OK, thanks. :-)

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