gdb crashed with SIGABRT in dump_core()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gdb (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Nothing more to say
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gdb 7.11.1-
ProcVersionSign
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Nov 19 14:55:36 2016
ExecutablePath: /usr/bin/gdb
ProcCmdline: /usr/bin/gdb -ex attach\ 3512 --ex info\ threads --ex thread\ apply\ all\ bt --batch
ProcEnviron:
LANGUAGE=fr_FR:en
PATH=(custom, user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: gdb
StacktraceTop:
dump_core ()
?? ()
internal_verror ()
internal_error ()
?? ()
Title: gdb crashed with SIGABRT in dump_core()
UpgradeStatus: Upgraded to xenial on 2016-08-18 (93 days ago)
UserGroups: adm admin audio cdrom dialout dip disk docker fax floppy fuse libvirtd lp lpadmin netdev plugdev powerdev pulse pulse-access root sambashare sudo tape video wireshark
| Xavier Poinsard (xpoinsard) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1544144, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.