This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb eats 100% cpu for relative long time when I single step one instruction
- From: Daniel Jacobowitz <drow at false dot org>
- To: Thomas Glanzmann <sithglan at stud dot uni-erlangen dot de>,gdb at sources dot redhat dot com
- Date: Mon, 27 Jun 2005 17:48:26 -0400
- Subject: Re: gdb eats 100% cpu for relative long time when I single step one instruction
- References: <20050627212704.GD8659@cip.informatik.uni-erlangen.de>
On Mon, Jun 27, 2005 at 11:27:04PM +0200, Thomas Glanzmann wrote:
> This happens *only* when I call 'layout asm' gdb thinks that I am in the
> function jzero_far which is at 0x81cd12a but I am actually in a funtion
> without a debugging symbol at 0x838fdcb, so I think the 'layout regs'
> tries to analyse this few thousand instructions or whatever. Is there a
> way to tell 'layout regs' to show only the few surrounding instructions?
These are just display panes. It sounds like something is broken
inside the TUI. You'll have to build a debuggable GDB and attach
another gdb to it to see what it's spinning on.
--
Daniel Jacobowitz
CodeSourcery, LLC