gdb crashed with SIGABRT in raise()

[Walter Garcia-Fontes]

Just got this crash while reporting another crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gdb 7.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Thu Sep 15 13:50:14 2011
ExecutablePath: /usr/bin/gdb
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: gdb --batch --ex file\ /usr/lib/x86_64-linux-gnu/colord/colord --ex core-file\ /tmp/tmpBT8mGi --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
Signal: 6
SourcePackage: gdb
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 internal_verror ()
Title: gdb crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-09-15 (0 days ago)
UserGroups:

[Apport retracing service (apport)]

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 #841693, 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.