This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/3] Trust readonly sections if target has memory protection
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: yao at codesourcery dot com, gdb-patches at sourceware dot org
- Date: Fri, 6 Sep 2013 07:52:05 -0700
- Subject: Re: [PATCH 0/3] 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> <83txhymr02 dot fsf at gnu dot org> <522990FF dot 30608 at codesourcery dot com> <83mwnqmj8f dot fsf at gnu dot org> <20130906130332 dot GE3001 at adacore dot com> <8361uem5yv dot fsf at gnu dot org>
> > IMO, XP is probably the most ancient version that would be reasonable
> > to support. Are people still developping on more ancient versions?
>
> If we support XP, extending support to Windows 2000 or even NT 4.0
> comes almost at no cost. IMO, there's no need to drop support for
> platforms whose support doesn't impose any tangible maintenance
> headaches.
>
> Windows 9X can be easily recognized at run time, and the feature that
> is the subject of this thread can be turned off then.
Perhaps a compromise: For the new feature to fail, it'd need an
extremely ancient version of Windows, coupled with a bad program
that writes outside of its memory area. How about we forgo the
Windows 9x detection, and just enable the feature on Windows
unconditionally? This removes the burden from Yao, who shouldn't
be asked to do this work unless he wants to. Then, if someone
believes it's necessary to turn the feature off by default on
old versions of Windows, it should be easy for them to do so.
--
Joel