Bug 615680 - [abrt] crash in gdb-7.1-28.fc13: gdbpy_is_string: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gdb-7.1-28.fc13: gdbpy_is_string: Process /usr/bin/gdb was ki...
Keywords:
Status: CLOSED DUPLICATE of bug 611569
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:030e2fc8ce975450db0cda1c217...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-17 22:46 UTC by Kyryl Bilokurov
Modified: 2010-07-19 17:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-19 17:19:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (11.58 KB, text/plain)
2010-07-17 22:47 UTC, Kyryl Bilokurov 		no flags Details
View All

Description Kyryl Bilokurov 2010-07-17 22:46:57 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /usr/bin/krita' -ex 'core-file /var/cache/abrt/ccpp-1279404416-8680/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: gdbpy_is_string
executable: /usr/bin/gdb
global_uuid: 030e2fc8ce975450db0cda1c2175defc77ed77cf
kernel: 2.6.33.6-147.fc13.x86_64
package: gdb-7.1-28.fc13
rating: 4
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. generating backtrace for krita crash
2.
3.
Comment 1 Kyryl Bilokurov 2010-07-17 22:47:00 UTC 
Created attachment 432647 [details]
File: backtrace
Comment 2 Jan Kratochvil 2010-07-19 17:19:26 UTC 

*** This bug has been marked as a duplicate of bug 611569 ***
Note You need to log in before you can comment on or make changes to this bug.