RE: [PATCH 0/3] Trust readonly sections if target has memory protection

["Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>]

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : vendredi 6 septembre 2013 15:32
> À : Joel Brobecker
> Cc : yao@codesourcery.com; gdb-patches@sourceware.org
> Objet : Re: [PATCH 0/3] Trust readonly sections if target has memory
> protection
> 
> > Date: Fri, 6 Sep 2013 06:03:32 -0700
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
> >
> > > MinGW doesn't support Windows 3.x, and I think Cygwin doesn't support
> > > 9x anymore.
> >
> > IMO, XP is probably the most ancient version that would be reasonable
> > to support. Are people still developping on more ancient versions?

  I have a question:
if Windows OS is supposed to support memory protection,
then why is it allowed to set software interrupts?
  We do overwrite the .text section of the debuggee to do this, no?

  Does this simply mean that the program itself would not be allowed
to modify its own .text section (or any other read-only section), 
but that the debugger has a higher privilege, which allows him 
to overwrite read-only sections...

  If this is true, does it mean that if we "set trust-readonly-sections
auto" 
and use the debugger to overwrite any memory in READ_ONLY section,
and read it back subsequently, it will still display the unmodified memory?

  Is the "feature/problem" limited to use of gdbserver?

  Is the behavior the same on Linux systems?

 Pierre Muller