>Number: 2345
>Category: gdb
>Synopsis: GDB 6.7 - ptype $pc or whatis $pc causes internal-error:
>register_type
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sun Oct 21 18:58:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator: r chapman
>Release: GNU gdb 6.7 (made from gdb-6.7.tar.bz2)
>Organization:
>Environment:
OS:
Linux localhost.localdomain 2.6.9-55.0.9.EL #1 Thu Sep 27 18:10:45 EDT
2007 i686 i686 i386 GNU/Linux
[Centos 4.5]
Compiler: GCC
Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/manr
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-java-awt=gtk
--host=i386-redhat-linux
Thread model: posix
gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)
GDB Config:
This GDB was configured as "i686-pc-linux-gnu".
>Description:
Either of the commands "whatis $pc" or "ptype $pc" produce a gdb internal-error
and the options to quit a potentially
unreliable debugging session and create a core file of GDB.
This may be a misuse of the 'ptype' and 'whatis' commands
but, if so, couldn't gdb handle it with a little more grace?
Sample error output follows:
(gdb) whatis $pc
../../gdb-6.7/gdb/regcache.c:164: internal-error: register_type:
Assertion `regnum >= 0 && regnum < descr->nr_cooked_registers' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
../../gdb-6.7/gdb/regcache.c:164: internal-error: register_type:
Assertion `regnum >= 0 && regnum < descr->nr_cooked_registers' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
|
