Bug 638208

Summary: [abrt] gdb-7.2-15.fc14: dl_main: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: BRARD <jean01brard>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: fweimer, jakub, jan.kratochvil, pmuldoon, schwab
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:3aa3cfd50298b07231f21cc846fec42fe9da0955
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-28 16:14:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description BRARD 2010-09-28 14:01:51 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /usr/lib/xulrunner-1.9.2/mozilla-xremote-client' -ex 'core-file /var/spool/abrt/ccpp-1285681774-31110/coredump' -ex 'thread apply all backtrace 2048 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info registers' -ex disassemble
component: gdb
crash_function: dl_main
executable: /usr/bin/gdb
kernel: 2.6.35.4-28.fc14.i686
package: gdb-7.2-15.fc14
rating: 4
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1285682273
uid: 500

How to reproduce
-----
Signalement à répétition de bug à chaque fois que j'utilise abrt
2.
3.
Comment 1 BRARD 2010-09-28 14:01:55 UTC 
Created attachment 450208 [details]
File: backtrace
Comment 2 BRARD 2010-09-28 14:02:56 UTC 
Package: gdb-7.2-15.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.id à précédent
2.
3.
Comment 3 Andreas Schwab 2010-09-28 16:14:13 UTC 

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