From: Daniel Jacobowitz <drow@false.org>
To: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>, gdb@sources.redhat.com
Subject: Re: gdb eats 100% cpu for relative long time when I single step one instruction
Date: Mon, 27 Jun 2005 21:48:00 -0000 [thread overview]
Message-ID: <20050627214826.GA756@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2005-06-27 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 21:27 Thomas Glanzmann
2005-06-27 21:48 ` Daniel Jacobowitz [this message]
2005-06-27 21:59 ` Thomas Glanzmann
2005-06-27 22:02 ` Daniel Jacobowitz
2005-06-27 22:11 ` Thomas Glanzmann
2005-06-28 12:27 ` Thomas Glanzmann
2005-06-28 13:13 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050627214826.GA756@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=sithglan@stud.uni-erlangen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox