Bug 1072331 - [abrt] gdb: dict_dealloc(): gdb killed by SIGSEGV
Summary: [abrt] gdb: dict_dealloc(): gdb killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:c52407b534fc8330eab6f57ee58...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-04 11:54 UTC by Serge Matveenko
Modified: 2015-06-29 19:14 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:14:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (19.84 KB, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: cgroup (156 bytes, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: core_backtrace (4.27 KB, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: dso_list (6.00 KB, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: environ (311 bytes, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: exploitable (82 bytes, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: limits (1.29 KB, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: maps (22.16 KB, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: open_fds (461 bytes, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: proc_pid_status (902 bytes, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details
File: var_log_messages (519 bytes, text/plain)
2014-03-04 11:54 UTC, Serge Matveenko
no flags Details

Description Serge Matveenko 2014-03-04 11:54:27 UTC
Version-Release number of selected component:
gdb-7.6.50.20130731-19.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        gdb -batch -ex 'set debug-file-directory /' -ex 'file /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre-abrt/bin/java' -ex 'core-file ./coredump' -ex 'thread apply all backtrace 1024 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info all-registers' -ex disassemble
crash_function: dict_dealloc
executable:     /usr/bin/gdb
kernel:         3.13.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 dict_dealloc at /usr/src/debug/Python-2.7.5/Objects/dictobject.c:1019
 #1 insertdict_by_entry at /usr/src/debug/Python-2.7.5/Objects/dictobject.c:528
 #2 dict_set_item_by_hash_or_entry at /usr/src/debug/Python-2.7.5/Objects/dictobject.c:774
 #3 PyDict_SetItem at /usr/src/debug/Python-2.7.5/Objects/dictobject.c:827
 #4 _PyModule_Clear at /usr/src/debug/Python-2.7.5/Objects/moduleobject.c:138
 #5 PyImport_Cleanup at /usr/src/debug/Python-2.7.5/Python/import.c:508
 #6 Py_Finalize at /usr/src/debug/Python-2.7.5/Python/pythonrun.c:454
 #7 do_my_cleanups at ../../gdb/cleanups.c:155
 #8 do_final_cleanups at ../../gdb/cleanups.c:186
 #9 quit_force at ../../gdb/top.c:1447

Comment 1 Serge Matveenko 2014-03-04 11:54:34 UTC
Created attachment 870359 [details]
File: backtrace

Comment 2 Serge Matveenko 2014-03-04 11:54:36 UTC
Created attachment 870360 [details]
File: cgroup

Comment 3 Serge Matveenko 2014-03-04 11:54:38 UTC
Created attachment 870361 [details]
File: core_backtrace

Comment 4 Serge Matveenko 2014-03-04 11:54:40 UTC
Created attachment 870362 [details]
File: dso_list

Comment 5 Serge Matveenko 2014-03-04 11:54:42 UTC
Created attachment 870363 [details]
File: environ

Comment 6 Serge Matveenko 2014-03-04 11:54:45 UTC
Created attachment 870364 [details]
File: exploitable

Comment 7 Serge Matveenko 2014-03-04 11:54:48 UTC
Created attachment 870365 [details]
File: limits

Comment 8 Serge Matveenko 2014-03-04 11:54:51 UTC
Created attachment 870366 [details]
File: maps

Comment 9 Serge Matveenko 2014-03-04 11:54:53 UTC
Created attachment 870367 [details]
File: open_fds

Comment 10 Serge Matveenko 2014-03-04 11:54:56 UTC
Created attachment 870368 [details]
File: proc_pid_status

Comment 11 Serge Matveenko 2014-03-04 11:54:58 UTC
Created attachment 870369 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-05-29 11:08:28 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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-06-29 19:14:41 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.