Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ping: [patch 1/6] PIE: Attach binary even after re-prelinked underneath
Date: Mon, 05 Jul 2010 17:06:00 -0000	[thread overview]
Message-ID: <20100705170602.GY2595@adacore.com> (raw)
In-Reply-To: <20100704101635.GA6875@host0.dyn.jankratochvil.net>

> gdb/
> 2010-07-02  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 	    Joel Brobecker  <brobecker@adacore.com>
> 
> 	Fix attaching to PIEs prelinked on the disk after the process was
> 	started.
> 	* solib-svr4.c (svr4_exec_displacement): New variable arch_size.
> 	Verify it against bfd_get_arch_size.  Try to match arbitrary
> 	displacement for the phdrs comparison.
> 
> gdb/testsuite/
> 2010-07-02  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 	    Joel Brobecker  <brobecker@adacore.com>
> 
> 	* gdb.base/break-interp.exp: Run $binpie with new value "ATTACH", new
> 	code for it.  New variable relink_args.
> 	(prelinkYES): Call prelinkNO.
> 	(test_attach): Accept new parameter relink_args.  Re-prelink the binary
> 	in such case.  Move the core code to ...
> 	(test_attach_gdb): ... a new function.  Send GDB command "file".
> 	Extend expected "Attaching to " string.

This is OK, with one English error in one of my suggestions (mea culpa).
I also still have a question, but this should not prevent the patch to
go in as is.

> +	      /* DISPLACEMENT could be found easier by the difference of
                                             ^^^^^^ more easily

Same thing for the 64bit case.

> +		  /* PT_GNU_STACK is an exception by being never relocated by
> +		     prelink as its addresses are always zero.  */

I understand why you mean, now, about the PT_GNU_STACK entry not being
changed during the prelink.  But I don't get the relationship between
this comment and the code surrounding it. Can you explain that?

-- 
Joel


  reply	other threads:[~2010-07-05 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 16:30 [patch 1/6]: " Jan Kratochvil
2010-03-29 16:15 ` [patch 1/6]: PIE: Attach binary even after re-prelinked underneath [repost] Jan Kratochvil
2010-06-09 15:08 ` ping: [patch 1/6] PIE: Attach binary even after re-prelinked underneath Jan Kratochvil
2010-06-29 17:49   ` Joel Brobecker
2010-07-04 10:17     ` Jan Kratochvil
2010-07-05 17:06       ` Joel Brobecker [this message]
2010-07-05 17:22         ` Jan Kratochvil
2010-07-05 17:49           ` Joel Brobecker
2010-07-05 18:09             ` Jan Kratochvil

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=20100705170602.GY2595@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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