From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: 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 22:11:00 -0000 [thread overview]
Message-ID: <20050627221140.GH8659@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20050627220236.GA1364@nevyn.them.org>
Hello,
> Sorry, this doesn't tell me much. I'd need backtraces inside GDB to
> know what it thinks it is doing.
Okay. I will recompile gdb tomorrow with debugging symbols and provide a
backtrace. Anything I should obey?
Thomas
next prev parent reply other threads:[~2005-06-27 22:11 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
2005-06-27 21:59 ` Thomas Glanzmann
2005-06-27 22:02 ` Daniel Jacobowitz
2005-06-27 22:11 ` Thomas Glanzmann [this message]
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=20050627221140.GH8659@cip.informatik.uni-erlangen.de \
--to=sithglan@stud.uni-erlangen.de \
--cc=gdb@sources.redhat.com \
/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