From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ping: [patch 3/6] PIE: Fix occasional error attaching i686 binary
Date: Tue, 29 Jun 2010 18:54:00 -0000 [thread overview]
Message-ID: <20100629185413.GT2595@adacore.com> (raw)
In-Reply-To: <20100609150841.GC7183@host0.dyn.jankratochvil.net>
> gdb/
> 2010-03-29 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * auxv.c (memory_xfer_auxv): Update attach comment.
> * solib-svr4.c (svr4_special_symbol_handling): Remove the call to
> svr4_relocate_main_executable.
> (svr4_solib_create_inferior_hook): Make the call to
> svr4_relocate_main_executable unconditional.
>
> gdb/testsuite/
> 2010-03-29 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.base/attach-pie-misread.exp, gdb.base/attach-pie-misread.c: New.
> * gdb.base/break-interp.exp (reach, test_core, test_ld): Require each
> displacement message exactly once.
This patch looks OK to me.
> /* ld_so_xfer_auxv is the only function safe for virtual executables being
> executed by valgrind's memcheck. As using ld_so_xfer_auxv is problematic
> - during inferior startup GDB does call it only for attached processes. */
> + during inferior startup as ld.so symbol tables are not yet relocated GDB
> + calls ld_so_xfer_auxv only for attached processes. */
Style: "As [...] as"... Suggest instead:
Using ld_so_xfer_auxv during inferior startup is problematic, because
ld.so symbol tables have not yet relocated yet. So GDB uses this function
only when attaching to a process.
--
Joel
next prev parent reply other threads:[~2010-06-29 18:54 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:09 ` ping: " Jan Kratochvil
2010-06-29 18:54 ` Joel Brobecker [this message]
2010-07-04 10:18 ` Jan Kratochvil
2010-07-05 17:18 ` Joel Brobecker
2010-07-05 18:11 ` 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=20100629185413.GT2595@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