From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [commit] [patch] Fix crash on `info files' with gdbserver
Date: Sun, 12 Feb 2012 19:16:00 -0000 [thread overview]
Message-ID: <20120212191601.GA25310@host2.jankratochvil.net> (raw)
In-Reply-To: <4F32E748.5020608@redhat.com>
On Wed, 08 Feb 2012 22:21:12 +0100, Pedro Alves wrote:
> That's the right choice. The exec target nowadays handles reading memory
> from all target sections, no matter whether they came from the executable
> or from shared libraries. So e.g., "set trust-readonly-sections" works
> with the DSOs target sections too.
Checked in:
http://sourceware.org/ml/gdb-cvs/2012-02/msg00065.html
Thanks for the review.
Jan
prev parent reply other threads:[~2012-02-12 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 20:50 Jan Kratochvil
2012-02-08 21:21 ` Pedro Alves
2012-02-12 19:16 ` Jan Kratochvil [this message]
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=20120212191601.GA25310@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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