gdb tui support broken ("layout regs" gives internal error, "layout split" gives core dump

Bug #676891 reported by James Hunt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gdb

The tui "layout" commands appear rather "fragile":

________________________________________________

1) "layout regs" causes a gdb internal error

To recreate:

gcc -g file.c
gdb --tui a.out
(gdb) b main
(gdb) layout regs
(gdb) r
Starting program: /home/james/src/c/a.out
/build/buildd/gdb-7.2/gdb/i386-linux-nat.c:562: internal-error: Got request for bad register number 41.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
________________________________________________

2) "layout split" causes gdb core dump

To recreate:

gcc -g file.c
gdb --tui a.out
(gdb) b main
(gdb) layout split
(gdb) r
Segmentation fault (core dumped)
________________________________________________

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gdb 7.2-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu Nov 18 09:29:40 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: gdb

Revision history for this message
James Hunt (jamesodhunt) wrote :
Revision history for this message
James Hunt (jamesodhunt) wrote :

Notes:

- problem occurs with and without ~/.gdbinit
- problem appears independent of terminal size (occurs with 24x80 and 48x143).

Revision history for this message
Matthias Klose (doko) wrote :

closing this rather old issue. sorry for not addressing this earlier. Please could you recheck with the recent 14.04 LTS or 14.10 releases and reopen the issue if the problem persists?

Changed in gdb (Ubuntu):
status: New → Invalid
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.