From: Tom Tromey <tromey@cygnus.com>
To: insight@sourceware.cygnus.com
Subject: Insight bug with assembly (?)
Date: Thu, 06 Apr 2000 15:48:00 -0000 [thread overview]
Message-ID: <87ya6qkfl2.fsf@cygnus.com> (raw)
Today I built the most recent cvs gdb on my x86 Debian 2.0 box.
I'm using an ancient (2.0.34) kernel.
I'm trying to debug stubs generated by gcj (the Java front end to
gcc). So, I set a breakpoint on the stub, and when it is hit I change
the view to assembly and "si" or "ni" through.
While debugging I did an "si" into a function call. The assembly for
the new function (call it "X") appeared. Good.
Then I re-ran the inferior using "r".
When the inferior stopped in my stub, the source window showed the
assembly for "X" and not my stub. Oops.
I tried "up" and "down" on the console, but that didn't help.
Pressing the "bottom of stack" button on the source window did help.
However, I shouldn't have to do this.
Sorry if this seems vague. It is reproducible using my setup, but I
haven't tried it on any other examples.
Tom
next reply other threads:[~2000-04-06 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-06 15:48 Tom Tromey [this message]
2000-04-06 15:56 ` James Ingham
2000-04-06 16:01 ` Tom Tromey
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=87ya6qkfl2.fsf@cygnus.com \
--to=tromey@cygnus.com \
--cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).