From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ping: [patch 2/6] PIE: Attach binary even after ld.so re-prelinked underneath
Date: Mon, 05 Jul 2010 17:15:00 -0000 [thread overview]
Message-ID: <20100705171443.GZ2595@adacore.com> (raw)
In-Reply-To: <20100704101653.GB6875@host0.dyn.jankratochvil.net>
V> Therefore used some merged+modified comment:
Much clearer, thank you (and I'm continuing to learn as I go)...
> gdb/
> 2010-07-04 Jan Kratochvil <jan.kratochvil@redhat.com>
> Joel Brobecker <brobecker@adacore.com>
>
> * auxv.c (ld_so_xfer_auxv): Do not error on failed read of data_address.
>
> gdb/testsuite/
> 2010-07-04 Jan Kratochvil <jan.kratochvil@redhat.com>
> Joel Brobecker <brobecker@adacore.com>
>
> * gdb.base/break-interp.exp (test_attach): Keep $interp changed. Move
OK with the tiny changes below.
> In most cases of a PIE running under valgrind there is no way how to find
^^^^^^^^^^^^^
no way to find
> # Formerly this test was testing only prelinking of $EXEC. As the
> # prelink command prelinks automatically even all $EXEC's libraries
automatically prelinks all of $EXEC's libraries,
(the comma is important)
> # even $INTERP got prelinked. Therefore we formerly had to
^^^ Therefore,
> # `[copy $interp_saved $interp]' to make $INTERP not affected by
> # this prelinking of $EXEC.
> #
> # But now we need to test even prelinking of $INTERP. We could
> # create a separate test to test just the $INTERP prelinking. For
> # the test simplicity we merged this test and the test above by not
^^^^ test simplicity, we merged [...]
> # restoring $INTERP after $EXEC prelink. $INTERP gets restored
> # later below.
--
Joel
next prev parent reply other threads:[~2010-07-05 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 16:17 Jan Kratochvil
2010-06-09 15:08 ` ping: " Jan Kratochvil
2010-06-29 18:21 ` Joel Brobecker
2010-07-04 10:17 ` Jan Kratochvil
2010-07-05 17:15 ` Joel Brobecker [this message]
2010-07-05 18:10 ` 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=20100705171443.GZ2595@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