Bug 1474578 - [abrt] gdb-headless: dump_core(): gdb killed by signal 6
Summary: [abrt] gdb-headless: dump_core(): gdb killed by signal 6
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 26
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sergio Durigan Junior
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:e78adebb2e7cd965defe996b366...
: 1507224 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-25 01:39 UTC by Dima Ryazanov
Modified: 2018-05-29 12:00 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:00:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (95.45 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: cgroup (289 bytes, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: core_backtrace (19.62 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: cpuinfo (1.34 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: dso_list (12.25 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: environ (2.64 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: limits (1.29 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: maps (51.20 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: open_fds (10.50 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: proc_pid_status (1.27 KB, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details
File: var_log_messages (294 bytes, text/plain)
2017-07-25 01:39 UTC, Dima Ryazanov
no flags Details

Description Dima Ryazanov 2017-07-25 01:39:05 UTC
Description of problem:
I got a crash in Epiphany, and tried reporting it. It failed to generate traces server-side, so I agreed to install debug info and retry locally. Then gdb crashed while trying to get the stack traces.

Version-Release number of selected component:
gdb-headless-8.0-13.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 3
cmdline:        /usr/libexec/gdb -batch -iex add-auto-load-safe-path /var/cache/abrt-di/usr/lib/debug -iex add-auto-load-scripts-directory /var/cache/abrt-di/usr/lib/debug -ex set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug -ex file /usr/libexec/webkit2gtk-4.0/WebKitWebProcess -ex core-file ./coredump -ex thread apply all -ascending 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: dump_core
executable:     /usr/libexec/gdb
journald_cursor: s=60c3f405f75945d5a6a994d97cd435f9;i=299d0;b=21ab01e2d8324da98ec20fcd5e1aca8f;m=cc6b028b;t=5550c9595e854;x=c0d36ee58bd9b4f0
kernel:         4.11.11-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 1419703

Comment 1 Dima Ryazanov 2017-07-25 01:39:10 UTC
Created attachment 1303962 [details]
File: backtrace

Comment 2 Dima Ryazanov 2017-07-25 01:39:11 UTC
Created attachment 1303963 [details]
File: cgroup

Comment 3 Dima Ryazanov 2017-07-25 01:39:13 UTC
Created attachment 1303964 [details]
File: core_backtrace

Comment 4 Dima Ryazanov 2017-07-25 01:39:14 UTC
Created attachment 1303965 [details]
File: cpuinfo

Comment 5 Dima Ryazanov 2017-07-25 01:39:15 UTC
Created attachment 1303966 [details]
File: dso_list

Comment 6 Dima Ryazanov 2017-07-25 01:39:16 UTC
Created attachment 1303967 [details]
File: environ

Comment 7 Dima Ryazanov 2017-07-25 01:39:17 UTC
Created attachment 1303968 [details]
File: limits

Comment 8 Dima Ryazanov 2017-07-25 01:39:18 UTC
Created attachment 1303969 [details]
File: maps

Comment 9 Dima Ryazanov 2017-07-25 01:39:19 UTC
Created attachment 1303970 [details]
File: open_fds

Comment 10 Dima Ryazanov 2017-07-25 01:39:20 UTC
Created attachment 1303971 [details]
File: proc_pid_status

Comment 11 Dima Ryazanov 2017-07-25 01:39:21 UTC
Created attachment 1303972 [details]
File: var_log_messages

Comment 12 Dima Ryazanov 2017-07-25 01:41:06 UTC
Small correction: the original crash was one of the tabs in Epiphany (after I opened the web inspector), not the main process.

Comment 13 Jan Niklas Hasse 2017-10-28 13:08:20 UTC
*** Bug 1507224 has been marked as a duplicate of this bug. ***

Comment 14 Fedora End Of Life 2018-05-03 08:36:11 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 15 Fedora End Of Life 2018-05-29 12:00:39 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.