This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Is nexti confused by pushq?
- From: dwk <dwks42 at gmail dot com>
- To: David Griffiths <dgriffiths at undo dot io>
- Cc: GDB <gdb at sourceware dot org>
- Date: Mon, 25 Feb 2019 10:54:19 -0500
- Subject: Re: Is nexti confused by pushq?
- References: <CA++j6c4bKPiWgYsSp2ajPLrJmv4wQ6Fb_Z=nXfs7TTOjzAqKRg@mail.gmail.com>
I encounter this frequently, although I don't have a minimal case yet
either. I think it may have something to do with symbol information, as
I've only encountered the case when symbol information is not present (as
in the example you gave). stepi always works but nexti sometimes turns into
a continue, I assumed because it was unable to figure out where the "next"
instruction was somehow in the absence of symbols.
dwk
On Mon, Feb 25, 2019, 10:41 AM David Griffiths <dgriffiths@undo.io> wrote:
> Hi, when I get to the following instructions:
>
> 0x00007fffe192413e: rex.W pushq 0x28(%rsp)
> 0x00007fffe1924143: rex.W popq (%rsp)
> 0x00007fffe1924147: callq 0x00007fffe1045de0
>
> and do "nexti" at the first, it doesn't stop at the second but instead acts
> as though I'd done "continue". For some reason I can't reproduce with a
> little test though.
>
> (gdb 8.1 on Ubuntu 16.04)
>
> BTW I'm doing nexti programmatically and trying to avoid looking at the
> next instruction to decide whether to do stepi or nexti.
>
> Cheers,
>
> David
>
> --
>
> David Griffiths, Senior Software Engineer
>
> Undo <https://undo.io> | Resolve even the most challenging software
> defects
> with software flight recorder technology
>
> Software reliability report: optimizing the software supplier and customer
> relationship
> <
> https://info.undo.io/software-reliability-report-optimizing-supplier-and-customer-relationship
> >
>