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: Eli Zaretskii <eliz at gnu dot org>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 06 Sep 2013 17:38:03 +0300
- 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> <"000d01ceab0b$d53ae600$7fb0b200$ at muller"@ics-cnrs.unistra.fr>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Date: Fri, 6 Sep 2013 16:17:34 +0200
>
> I have a question:
> if Windows OS is supposed to support memory protection,
> then why is it allowed to set software interrupts?
What do you mean by "set software interrupts", in the context of
Windows debugging?
> We do overwrite the .text section of the debuggee to do this, no?
I don't think so, but maybe I misunderstand what you mean.