Bug 614269 - [abrt] crash in cgdb-0.6.5-1.fc12: ___fprintf_chk: Process /usr/bin/cgdb was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in cgdb-0.6.5-1.fc12: ___fprintf_chk: Process /usr/bin/cgdb was ...
Alias: None
Product: Fedora
Classification: Fedora
Component: cgdb   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Gilboa Davara
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:b22a07c13b2b89a9072b210c565...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-14 01:03 UTC by igor.redhat@gmail.com
Modified: 2010-12-03 13:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 13:16:04 UTC
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 (11.17 KB, text/plain)
2010-07-14 01:03 UTC, igor.redhat@gmail.com
no flags Details

Description igor.redhat@gmail.com 2010-07-14 01:03:53 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: cgdb convert_decimal
comment: I exited in the middle of debugging...
component: cgdb
crash_function: ___fprintf_chk
executable: /usr/bin/cgdb
global_uuid: b22a07c13b2b89a9072b210c565c8b2e4365f478
package: cgdb-0.6.5-1.fc12
rating: 4
reason: Process /usr/bin/cgdb was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 igor.redhat@gmail.com 2010-07-14 01:03:55 UTC
Created attachment 431638 [details]
File: backtrace

Comment 2 Gilboa Davara 2010-07-23 06:36:38 UTC
Can you some additional information? (What was debugged, what were you doing when cgdb crashed, etc)

- Gilboa

Comment 3 igor.redhat@gmail.com 2010-07-23 22:07:04 UTC
I wish I could give you more info but there isn't much. I was debugging a tiny test program; the crash happened when I tried to exit cgdb in the middle of the debugging session (i.e., the program was running) - with Ctrl-D just in case that matters. Unfortunately, I made some changes and recompiled immediately after the crash and has never been able to reproduce it since. It's quite possible that my code was corrupting the heap in some way but I can't tell for sure anymore...

Comment 4 Bug Zapper 2010-11-03 11:59:21 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 5 Gilboa Davara 2010-11-04 11:22:48 UTC
I'm working on a somewhat newer version of cgdb, but I cannot seem to reproduce this crash.
Reopen if you somehow manage to hit it again.

- Gilboa

Comment 6 Bug Zapper 2010-12-03 13:16:04 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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