From: David Griffiths <dgriffiths@undo.io>
To: gdb@sourceware.org
Subject: Is nexti confused by pushq?
Date: Mon, 25 Feb 2019 15:40:00 -0000 [thread overview]
Message-ID: <CA++j6c4bKPiWgYsSp2ajPLrJmv4wQ6Fb_Z=nXfs7TTOjzAqKRg@mail.gmail.com> (raw)
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>
next reply other threads:[~2019-02-25 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 15:40 David Griffiths [this message]
2019-02-25 15:54 ` dwk
2019-02-26 7:32 ` Andrew Burgess
2019-02-26 10:12 ` Jan Kratochvil
2019-02-26 11:50 ` David Griffiths
2019-02-26 11:58 ` Jan Kratochvil
2019-02-26 14:19 ` Dmitry Samersoff
2019-02-26 14:42 ` David Griffiths
2019-02-26 19:05 ` Tom Tromey
2019-02-27 7:59 ` Dmitry Samersoff
2019-02-27 14:53 ` 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='CA++j6c4bKPiWgYsSp2ajPLrJmv4wQ6Fb_Z=nXfs7TTOjzAqKRg@mail.gmail.com' \
--to=dgriffiths@undo.io \
--cc=gdb@sourceware.org \
/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).