Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 620255 - [abrt] crash in gdb-7.1-30.fc13: preserve_one_value: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
[abrt] crash in gdb-7.1-30.fc13: preserve_one_value: Process /usr/bin/gdb was...
Status: CLOSED DUPLICATE of bug 627456
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-08-01 15:36 EDT by jan p. springer
Modified: 2010-11-08 12:25 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-08 12:25:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (10.14 KB, text/plain)
2010-08-01 15:36 EDT, jan p. springer
no flags Details

  None (edit)
Description jan p. springer 2010-08-01 15:36:21 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gdb --args ./bin/editor --no-signal-handler
component: gdb
crash_function: preserve_one_value
executable: /usr/bin/gdb
global_uuid: bf5cae00ccf05d9fabbdddbc7eebf0f5b3d0a73f
package: gdb-7.1-30.fc13
rating: 4
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 jan p. springer 2010-08-01 15:36:23 EDT
Created attachment 435911 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 12:25:41 EST

*** This bug has been marked as a duplicate of bug 627456 ***
Comment 3 Karel Klíč 2010-11-08 12:25:41 EST
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 #627456.

Sorry for the inconvenience.

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