Bug 919271 - [abrt] gdb-7.5.50.20130215-9.fc19: bfd_getl32: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Summary: [abrt] gdb-7.5.50.20130215-9.fc19: bfd_getl32: Process /usr/bin/gdb was kille...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2f6bd0e1f22116fbece2081923c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-08 00:11 UTC by Michael Schwendt
Modified: 2015-02-17 14:50 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:50:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (174.59 KB, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: cgroup (127 bytes, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: core_backtrace (3.27 KB, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: dso_list (1.58 KB, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: environ (2.12 KB, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: limits (1.29 KB, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: maps (31.18 KB, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: open_fds (1.01 KB, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: proc_pid_status (1.05 KB, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details
File: var_log_messages (298 bytes, text/plain)
2013-03-08 00:11 UTC, Michael Schwendt
no flags Details

Description Michael Schwendt 2013-03-08 00:11:27 UTC
Description of problem:
The crash is related to ABRT using gdb.

Version-Release number of selected component:
gdb-7.5.50.20130215-9.fc19

Additional info:
backtrace_rating: 4
cmdline:        gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /usr/bin/report-gtk' -ex 'core-file ./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
crash_function: bfd_getl32
executable:     /usr/bin/gdb
kernel:         3.9.0-0.rc0.git15.1.fc19.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 bfd_getl32 at ../../bfd/libbfd.c:623
 #1 read_initial_length at ../../gdb/dwarf2read.c:14596
 #2 read_comp_unit_head at ../../gdb/dwarf2read.c:3926
 #3 read_and_check_comp_unit_head at ../../gdb/dwarf2read.c:4012
 #4 init_cutu_and_read_dies at ../../gdb/dwarf2read.c:4544
 #5 load_full_comp_unit at ../../gdb/dwarf2read.c:6740
 #6 load_cu at ../../gdb/dwarf2read.c:2277
 #7 dw2_do_instantiate_symtab at ../../gdb/dwarf2read.c:2303
 #8 dw2_instantiate_symtab at ../../gdb/dwarf2read.c:2327
 #9 dw2_lookup_symbol at ../../gdb/dwarf2read.c:3263

Comment 1 Michael Schwendt 2013-03-08 00:11:32 UTC
Created attachment 706859 [details]
File: backtrace

Comment 2 Michael Schwendt 2013-03-08 00:11:35 UTC
Created attachment 706860 [details]
File: cgroup

Comment 3 Michael Schwendt 2013-03-08 00:11:38 UTC
Created attachment 706861 [details]
File: core_backtrace

Comment 4 Michael Schwendt 2013-03-08 00:11:40 UTC
Created attachment 706862 [details]
File: dso_list

Comment 5 Michael Schwendt 2013-03-08 00:11:43 UTC
Created attachment 706863 [details]
File: environ

Comment 6 Michael Schwendt 2013-03-08 00:11:45 UTC
Created attachment 706864 [details]
File: limits

Comment 7 Michael Schwendt 2013-03-08 00:11:48 UTC
Created attachment 706865 [details]
File: maps

Comment 8 Michael Schwendt 2013-03-08 00:11:51 UTC
Created attachment 706866 [details]
File: open_fds

Comment 9 Michael Schwendt 2013-03-08 00:11:53 UTC
Created attachment 706867 [details]
File: proc_pid_status

Comment 10 Michael Schwendt 2013-03-08 00:11:55 UTC
Created attachment 706868 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2013-04-03 15:08:51 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 12 Fedora End Of Life 2015-01-09 17:45:01 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 13 Fedora End Of Life 2015-02-17 14:50:35 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.