gdb crashed with NullPyObjectPtr in field()

Bug #543624 reported by igi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: gdb

The crash occurred on boot.

ProblemType: Crash
Architecture: i386
Date: Sun Mar 21 19:07:51 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gdb
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Package: gdb 7.0.90.20100311-0ubuntu1
ProcCmdline: gdb --batch --ex file\ /usr/bin/python2.6 --ex core-file\ /tmp/tmpDOr_pw --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:
 PATH=(custom, no user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
 LC_MESSAGES=C
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic-pae
SourcePackage: gdb
Title: gdb crashed with NullPyObjectPtr in field()
Uname: Linux 2.6.32-16-generic-pae i686
UserGroups:

Revision history for this message
igi (igor-cali) wrote :
tags: removed: need-duplicate-check
Matthias Klose (doko)
visibility: private → public
igi (igor-cali)
Changed in gdb (Ubuntu):
status: New → Fix Released
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.