gdb crashed with RuntimeError in field()

Bug #546702 reported by Salvatore Vassallo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gdb

In Lucid Gdb crashes after apport started

Gdb version 7.1-1ubuntu1

ProblemType: Crash
Architecture: i386
Date: Thu Mar 25 08:46:09 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gdb
Package: gdb 7.1-1ubuntu1
ProcCmdline: gdb --batch --ex file\ /usr/bin/python2.6 --ex core-file\ /tmp/tmp_He6Mh --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ (char*)\ __abort_msg
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: gdb
Title: gdb crashed with RuntimeError in field()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse pulse-access sambashare

Revision history for this message
Salvatore Vassallo (vassallosalvatore) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #548723, 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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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