gdb crashed with SIGABRT in __kernel_vsyscall()

[vishal Ithape]

Gdb crashed i was using virtualbox and while using scale plugin it suddenly crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gdb 7.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
Architecture: i386
Date: Mon Sep 5 15:34:39 2011
ExecutablePath: /usr/bin/gdb
ProcCmdline: gdb --batch --ex file\ /usr/sbin/modem-manager --ex core-file\ /tmp/tmpKUefwL --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:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
 ?? ()
Title: gdb crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 dump_core () at /build/buildd/gdb-7.3/gdb/utils.c:1053
 internal_vproblem (problem=0x84c5a54, file=0x8363bd8 "/build/buildd/gdb-7.3/gdb/linux-thread-db.c", line=1062, fmt=0x8363ba1 "%s: Assertion `%s' failed.", ap=0xbfc04d7c "\321D6\b\307@6\b8+") at /build/buildd/gdb-7.3/gdb/utils.c:1211
 internal_verror (file=0x8363bd8 "/build/buildd/gdb-7.3/gdb/linux-thread-db.c", line=1062, fmt=0x8363ba1 "%s: Assertion `%s' failed.", ap=0xbfc04d7c "\321D6\b\307@6\b8+") at /build/buildd/gdb-7.3/gdb/utils.c:1236
 internal_error (file=0x8363bd8 "/build/buildd/gdb-7.3/gdb/linux-thread-db.c", line=1062, string=0x8363ba1 "%s: Assertion `%s' failed.") at /build/buildd/gdb-7.3/gdb/utils.c:1246
 attach_thread (ptid=..., th_p=0xbfc04f88, ti_p=0xbfc04de0) at /build/buildd/gdb-7.3/gdb/linux-thread-db.c:1062

[Launchpad Janitor (janitor)]

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

[Matthias Klose (doko)]

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel free to re-open the issue if the problem persists.