This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/7 V2] Trust readonly sections if target has memory protection
- From: Yao Qi <yao at codesourcery dot com>
- To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- Cc: <gdb-patches at sourceware dot org>
- Date: Fri, 13 Sep 2013 16:16:44 +0800
- Subject: Re: [PATCH 0/7 V2] Trust readonly sections if target has memory protection
- Authentication-results: sourceware.org; auth=none
- References: <1378432920-7731-1-git-send-email-yao at codesourcery dot com> <1378641807-24256-1-git-send-email-yao at codesourcery dot com> <201309091916 dot r89JGbpf009986 at glazunov dot sibelius dot xs4all dot nl> <522E9A8A dot 7040509 at codesourcery dot com> <52317B66 dot 3020602 at codesourcery dot com> <201309120949 dot r8C9nFsJ016506 at glazunov dot sibelius dot xs4all dot nl>
On 09/12/2013 05:49 PM, Mark Kettenis wrote:
I'm certainly not outright rejecting it. But you'll certainly need to
rethink in which contexts it is safe/acceptable that "auto" actually
turns on the trust-readonly-sections feature. That decision should
probably be done on a per-architecture, per-OS basis, and only for
remote debugging.
Yeah, that is reasonable to me. Then, the proposed scope could be
{x86, x86_64}-{linux,mingw,cygwin} for remote debugging only. What do
you think?
I am fine to extend this scope to all linux targets, as what I did in
my patches, but looks it is safe to keep this set small at the
beginning.
--
Yao (éå)