emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Suggestion for gdb-ui.el


From: Nick Roberts
Subject: Suggestion for gdb-ui.el
Date: Wed, 1 Jun 2005 09:40:56 +1200

 > My inline asm uses the SSE floating point registers xmm0-xmm7.
 > Space toggles between "info registers" and "info all-registers"
 > mode in the *registers* buffer (M-x gdb-display-registers-buffer).
 > When all registers are shown they dont fit in the *registers*
 > buffer so I scroll down a bit to the xmm registers. But after each
 > stepi (step one instruction) the *registers* buffer scrolls
 > back to the Top again.
 >
 > * Suggestion: Update lisp/progmodes/gdb-ui.el so the *registers* buffer
 > somehow remembers the line number and scrolls back to the same line
 > after updating the registers.

The code was meant to do this but didn't because of an issue with point
and window point.  If you update from the repository this should work now.

 > It would also be nice if the changed registers would be highlighted
 > somehow (I noticed it's on the TODO list in gdb-ui.el).

This shouldn't be too hard to do with the GDB/MI commands.  I have other
changes that also use GDB/MI but I am waiting till after the release before
installing them in case such changes introduce bugs.  How useful is this
feature? I've not done low-level debugging or watched the contents of the
registers.  What debugging situations require this?  Are you debugging a
disassembly view in GDB from C code, or assembler (either generated by the
compiler or hand written) directly.

 > * Small bug: It is not possible to click two times on the same icon in
 > the gdb-ui toolbar (for instance next or stepi) without first moving the
 > mouse cursor outside the icon. Emacs was configured with --with-gtk and
 > I dont know if the bug exists with other toolkits. I tried it on
 > both Debian/Sarge (XFree86 4.3.0) and on Ubuntu/Hoary (X.org 6.8.2).
 > They both have the same GTK+ version (2.6.4).

I've not seen this with Mandrake 9.0. It might be because I've been fiddling
with the code that displays disassembly.  Perhaps Jan Djarv knows if it's a
GTK problem.

Nick




reply via email to

[Prev in Thread] Current Thread [Next in Thread]