Bug 687940 - [abrt] gdb-7.2-46.fc14: dump_core: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Summary: [abrt] gdb-7.2-46.fc14: dump_core: Process /usr/bin/gdb was killed by signal ...
Keywords:
Status: CLOSED DUPLICATE of bug 683068
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7d3132717acb6c186f0ddf7c7f6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 18:54 UTC by Radu Creanga
Modified: 2011-03-16 06:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 06:15:23 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (11.92 KB, text/plain)
2011-03-15 18:54 UTC, Radu Creanga
no flags Details

Description Radu Creanga 2011-03-15 18:54:17 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 12202 bytes
cmdline: gdb -q -nw -i mi -tty /dev/pts/1 --cd=/home/radu/workspace/test --command=.gdbinit /home/radu/workspace/test/Debug/test
comment: Was working on a simple 1 - file project in Eclipse Phortran for a class. Performed a series of debug / run actions and closed Eclipse. I don't think any tasks were running in Eclipse when i closed it. Recieved the crash notification right after closing Eclipse.
component: gdb
Attached file: coredump, 6631424 bytes
crash_function: dump_core
executable: /usr/bin/gdb
kernel: 2.6.35.11-83.fc14.i686
package: gdb-7.2-46.fc14
rating: 4
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1300214403
uid: 500

How to reproduce
-----
1. I was working in Eclipse Phortran on a simple 1-file project.
2. Performed a series of debug build / run actions.
3. Closed Eclipse.

Comment 1 Radu Creanga 2011-03-15 18:54:19 UTC
Created attachment 485582 [details]
File: backtrace

Comment 2 Jan Kratochvil 2011-03-16 06:15:23 UTC

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


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