This is the mail archive of the
insight@sourceware.cygnus.com
mailing list for the Insight project.
Re: Insight bug with assembly (?)
- To: tromey at cygnus dot com
- Subject: Re: Insight bug with assembly (?)
- From: James Ingham <jingham at cygnus dot com>
- Date: Thu, 6 Apr 2000 15:59:22 -0700 (PDT)
- Cc: insight at sourceware dot cygnus dot com
- References: <87ya6qkfl2.fsf@cygnus.com>
Tom,
Does the same thing happen when you rerun using the "Run" button?
I am not sure that "r" in the console and the run button are totally
synched up.
Just a thought...
Jim
> 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
>