From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 14/15] PIE: Fix back valgrind --db-attach=yes [fixup]
Date: Wed, 13 Jan 2010 21:08:00 -0000 [thread overview]
Message-ID: <m3fx69hfwa.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100110214208.GA1435@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Sun, 10 Jan 2010 22:42:08 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> `valgrind --db-attach=yes' will run GDB on the crashed PID which is only
Jan> a virtual emulated program inside a virtual machine running at that PID.
Jan> The /proc/PID/exe program is a valgrind tool (such as `memcheck').
[...]
Thanks for the detailed explanation.
This was very helpful.
Jan> gdb/
Jan> Support Valgrind attachments broken by the PIE support.
Jan> * auxv.c: Include gdbcore.h.
Jan> (procfs_xfer_auxv): Make static. Reduce its comment. Drop its
Jan> parameters ops, object and annex. Remove their assertions.
Jan> (ld_so_xfer_auxv, memory_xfer_auxv): New function.
Jan> * auxv.h (procfs_xfer_auxv): Remove comment. Rename to ...
Jan> (memory_xfer_auxv): ... here.
Jan> * linux-nat.c (linux_xfer_partial): Rename procfs_xfer_auxv to
Jan> memory_xfer_auxv.
Jan> * procfs.c (procfs_xfer_partial): Likewise.
Jan> * solib-svr4.c (svr4_relocate_main_executable): New prototype.
Jan> (svr4_special_symbol_handling): Call svr4_relocate_main_executable.
Jan> (svr4_solib_create_inferior_hook): Conditionalize the
Jan> svr4_relocate_main_executable call.
Jan> gdb/testsuite/
Jan> * gdb.base/valgrind-db-attach.exp, gdb.base/valgrind-db-attach.c: New.
Ok. Thanks.
Tom
next prev parent reply other threads:[~2010-01-13 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 21:01 [patch 14/15] PIE: Fix back valgrind --db-attach=yes Jan Kratochvil
2010-01-10 21:43 ` [patch 14/15] PIE: Fix back valgrind --db-attach=yes [fixup] Jan Kratochvil
2010-01-13 21:08 ` Tom Tromey [this message]
2010-01-14 21:16 ` 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=m3fx69hfwa.fsf@fleche.redhat.com \
--to=tromey@redhat.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