Ubuntu
gdb package

gdb crashed with SIGABRT in dump_core()

Bug #1544144 reported by abbas
64
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

new message with relate to this crash too:
https://bugs.launchpad.net/ubuntu/+source/docky/+bug/1544142

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gdb 7.10.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Feb 10 19:26:17 2016
ExecutablePath: /usr/bin/gdb
InstallationDate: Installed on 2016-01-01 (40 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/bin/gdb -ex attach\ 3358 --ex info\ threads --ex thread\ apply\ all\ bt --batch
Signal: 6
SourcePackage: gdb
StacktraceTop:
 dump_core ()
 ?? ()
 internal_verror ()
 internal_error ()
 ?? ()
Title: gdb crashed with SIGABRT in dump_core()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
abbas (sampad-abbas1370) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 dump_core ()
 internal_vproblem ()
 internal_verror ()
 internal_error ()
 execute_cfa_program ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gdb (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gdb (Ubuntu):
status: New → Confirmed
Brian Murray (brian-murray)
information type: Private → Public
Revision history for this message
Alexander Vinbæk Strand (alexstrand7-o) wrote :

Same bug here in Ubuntu 16.04 Xenial

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.