Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: palves@redhat.com,    uweigand@de.ibm.com,    gdb-patches@sourceware.org
Subject: Re: [PATCH] create_internal_breakpoint: Apply gdbarch_skip_entrypoint.
Date: Sat, 08 Nov 2014 01:57:00 -0000	[thread overview]
Message-ID: <21597.30817.910963.546392@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <yjt2fvdu5umt.fsf@ruffy.mtv.corp.google.com>

Doug Evans writes:
 > Hi.
 > 
 > In glibc, _dl_debug_state is usually defined like this:
 > 
 > void
 > _dl_debug_state (void)
 > {
 > }
 > 
 > and thus on powerpc64le-linux this function does not require a TOC register.
 >
 > [...]
 > ...
 > -3      shlib events   keep y   0x00003fffb7fd8e40 <__GI__dl_debug_state> inf 1
 > ...
 > [...]
 > ...
 > -3      shlib events   keep y   0x0000100000020e48 <__GI__dl_debug_state+8> inf 1

For completeness sake,
You can also see the difference in the "shlib events" breakpoint,
but with _ovly_debug_state you can run it for yourself without
having to hack glibc.

There was a cut-n-paste error in the patch.
Fixed below.

2014-11-07  Doug Evans  <dje@google.com>

	* breakpoint.c (create_internal_breakpoint): Apply
	gdbarch_skip_entrypoint if it's defined.

diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index bd51f5d..1b5cf5f 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -3306,6 +3306,9 @@ create_internal_breakpoint (struct gdbarch *gdbarch,
 
   init_sal (&sal);		/* Initialize to zeroes.  */
 
+  if (gdbarch_skip_entrypoint_p (gdbarch))
+    address = gdbarch_skip_entrypoint (gdbarch, address);
+
   sal.pc = address;
   sal.section = find_pc_overlay (sal.pc);
   sal.pspace = current_program_space;


  reply	other threads:[~2014-11-08  1:57 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 [this message]
2014-11-10 12:58 ` Ulrich Weigand
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=21597.30817.910963.546392@ruffy2.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=uweigand@de.ibm.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