From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Michael Haupt <michael.haupt@oracle.com>
Cc: gdb@sourceware.org
Subject: Re: "optimized out" in spite of DWARF saying otherwise?
Date: Fri, 22 Mar 2013 07:37:00 -0000 [thread overview]
Message-ID: <20130322073628.GA16757@host2.jankratochvil.net> (raw)
In-Reply-To: <89D4A69A-008A-4D56-9F2C-1F94AE41F62D@oracle.com>
On Thu, 21 Mar 2013 21:15:20 +0100, Michael Haupt wrote:
> The offending one I asked about is just a mark. There is no guarantee as to
> which instruction there is at the address in question; is it "safe" to use
> an extent of, say, 1, or does the instruction length govern that?
At least for GDB it is OK to use length 1 and IIUC the standard also
implicitly says so.
GDB+GCC use a special notation for calls: Address of the call instruction is
used before stepping in, call-instr-length - 1 address is used when inside the
callee and then normally address of next instruction after the call one when
the callee returns.
Regards,
Jan
prev parent reply other threads:[~2013-03-22 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 16:39 Michael Haupt
2013-03-21 16:48 ` Jan Kratochvil
2013-03-21 20:15 ` Michael Haupt
2013-03-22 7:37 ` Jan Kratochvil [this message]
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=20130322073628.GA16757@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=michael.haupt@oracle.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