Bug 596622 - [abrt] crash in gdb-7.0.1-45.fc12: get_frame_type: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
[abrt] crash in gdb-7.0.1-45.fc12: get_frame_type: Process /usr/bin/gdb was k...
Product: Fedora
Classification: Fedora
Component: gdb (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Jan Kratochvil
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-27 03:06 EDT by Adrin Jalali
Modified: 2010-06-01 09:29 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-01 09:29:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adrin Jalali 2010-05-27 03:06:34 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gdb -f -n -i=mi2 -directory=/home/adrin/Thesis/mosta_src/mosta/Debug/src -x /usr/share/anjuta/gdb.init /home/adrin/Thesis/mosta_src/mosta/Debug/src/mosta_anjuta
component: gdb
crash_function: get_frame_type
executable: /usr/bin/gdb
global_uuid: 55a386f0facd7f15d1f228700e3b0700ee60a3f4
package: gdb-7.0.1-45.fc12
rating: 3
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Jan Kratochvil 2010-06-01 09:29:51 EDT
There is no reproducer and for some reason no backtrace reported.
Cannot debug.

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