Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sources.redhat.com
Subject: Re: [patch] Strange stepping behaviour with ppc32 with secure PLTs
Date: Fri, 23 Jun 2006 21:06:00 -0000	[thread overview]
Message-ID: <1151092884.7608.82.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <20060520011451.GE22757@bubble.grove.modra.org>

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

It's been more than a month, so I thought I'd try again.

I also thought I'd try the new patch tracker:

:ADDPATCH PowerPC-32:

This patch fixes a problem gdb has 'next'ing over a call to a library
function on a ppc32 target program when secure PLT's are being used.  It
implements a 'GDB only solution' of the previous discussion on the
'gdb@' mailing list.

Here is that previous discussion:
http://sourceware.org/ml/gdb/2006-05/msg00154.html
and Daniel Jacobowitz's response:
http://sourceware.org/ml/gdb/2006-05/msg00155.html

Subsequent discussion on gdb-patches begins here:
http://sourceware.org/ml/gdb-patches/2006-05/msg00270.html
And peter out here:
http://sourceware.org/ml/gdb-patches/2006-05/msg00420.html

I have attached a update of the patch, now diff'ed against current
sources.

OK to commit?

-=# Paul #=-





[-- Attachment #2: keep-solib-tramp-sym.diff --]
[-- Type: text/x-patch, Size: 867 bytes --]

2006-06-23  Paul Gilliam  <pgilliam@us.ibm.com>

        * minsyms.c (lookup_minimal_symbol_by_pc_section): Don't ignore
        minimal symbols for solib trampolines just because they're in a
        different section than the PC.

Index: minsyms.c
===================================================================
RCS file: /cvs/src/src/gdb/minsyms.c,v
retrieving revision 1.45
diff -a -u -r1.45 minsyms.c
--- minsyms.c	17 Dec 2005 22:34:01 -0000	1.45
+++ minsyms.c	23 Jun 2006 20:59:34 -0000
@@ -486,6 +486,8 @@
 			  don't fill the bfd_section member, so don't
 			  throw away symbols on those platforms.  */
 		       && SYMBOL_BFD_SECTION (&msymbol[hi]) != NULL
+		       /* Don't ignoe symbols for solib tranpolines. */
+		       && MSYMBOL_TYPE (&msymbol[hi]) != mst_solib_trampoline
 		       && SYMBOL_BFD_SECTION (&msymbol[hi]) != section)
 		  --hi;
 

  reply	other threads:[~2006-06-23 21:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12 22:50 PAUL GILLIAM
2006-05-12 23:12 ` Daniel Jacobowitz
2006-05-13  1:46   ` PAUL GILLIAM
2006-05-13 14:58   ` Alan Modra
2006-05-13 15:13     ` Daniel Jacobowitz
2006-05-15  3:34       ` Alan Modra
2006-05-15 15:10         ` Daniel Jacobowitz
2006-05-16  2:07           ` Alan Modra
2006-05-16  2:35             ` Daniel Jacobowitz
2006-05-16  7:18             ` Mark Kettenis
2006-05-16 17:53               ` Alan Modra
2006-05-19 17:38                 ` PAUL GILLIAM
2006-05-20  1:32                   ` Alan Modra
2006-06-23 21:06                     ` PAUL GILLIAM [this message]
2006-06-23 21:22                       ` Daniel Jacobowitz

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=1151092884.7608.82.camel@dufur.beaverton.ibm.com \
    --to=pgilliam@us.ibm.com \
    --cc=amodra@bigpond.net.au \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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