This is the mail archive of the
insight-prs@sourceware.cygnus.com
mailing list for the Insight project.
insight/31: assembly update when re-running via console
- To: insight-gnats at sourceware dot cygnus dot com
- Subject: insight/31: assembly update when re-running via console
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 6 Apr 2000 23:09:10 -0000
- Reply-To: Tom Tromey <tromey at cygnus dot com>
- Resent-Cc: insight-prs at sourceware dot cygnus dot com
- Resent-Reply-To: insight-gnats@sourceware.cygnus.com, Tom Tromey <tromey@cygnus.com>
>Number: 31
>Category: insight
>Synopsis: assembly update when re-running via console
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Apr 06 16:13:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Tom Tromey
>Release: current cvs
>Organization:
>Environment:
Today I built the most recent cvs gdb on my x86 Debian 2.0 box.
I'm using an ancient (2.0.34) kernel.
>Description:
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.
>How-To-Repeat:
>Fix:
A workaround suggested by Jim is to use the
run button instead of using "r" from the console.
>Release-Note:
>Audit-Trail:
>Unformatted: