From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: dje@google.com (Doug Evans)
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] create_internal_breakpoint: Apply gdbarch_skip_entrypoint.
Date: Mon, 10 Nov 2014 12:58:00 -0000 [thread overview]
Message-ID: <201411101258.sAACwh1O008384@d03av02.boulder.ibm.com> (raw)
In-Reply-To: <yjt2fvdu5umt.fsf@ruffy.mtv.corp.google.com> from "Doug Evans" at Nov 07, 2014 05:49:30 PM
Doug Evans worte:
> This is important because the toolchain will optimize intra-module calls
> to skip the first two instructions that set up the TOC register.
> And since gdb currently doesn't to "entry point skipping" for internal
> breakpoints things work (in particular shlib event breakpoints).
Huh. Yes, that's clearly a bug.
> This patch fixes things by applying entry point skipping to
> internal breakpoints. Is this the best place to apply entry point
> skipping for internal breakpoints?
I think this is fine. (The alternative would be push it up into the
callers, which would have the advantage that you could do it only
for those callers that get the address from a symbol, and not those
that e.g. get it from a probe. However, since gdbarch_skip_entrypoint
is safe even if the address is not equal to a symbol address, it's
probably preferable to just do the skipping in one place.)
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2014-11-10 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 1:49 Doug Evans
2014-11-08 1:57 ` Doug Evans
2014-11-10 12:58 ` Ulrich Weigand [this message]
2014-11-10 15:45 ` Pedro Alves
2014-11-10 17:16 ` Ulrich Weigand
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=201411101258.sAACwh1O008384@d03av02.boulder.ibm.com \
--to=uweigand@de.ibm.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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