From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: Improve FAQ on early breakpoint for ASLR
Date: Fri, 4 Nov 2022 14:16:44 +0100 [thread overview]
Message-ID: <Y2UQvCw5NXNIYHTb@calimero.vinschen.de> (raw)
In-Reply-To: <4ccbb5e1-ee4f-8944-ed44-4af7fa79f048@dronecode.org.uk>
On Nov 4 12:53, Jon Turney wrote:
> On 04/11/2022 10:34, Corinna Vinschen wrote:
> > On Nov 3 11:22, Jeremy Drake via Cygwin-patches wrote:
> > > On Thu, 3 Nov 2022, Jon Turney wrote:
> > >
> > > > gdb supports 'set disable-randomization off' on Windows since [1]
> > > > (included in gdb 13).
> > > >
> > > > https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=bcb9251f029da8dcf360a4f5acfa3b4211c87bb0;hp=8fea1a81c7d9279a6f91e49ebacfb61e0f8ce008
> > >
> > > Is it really *disable*-randomization *off*? The double-negative seems to
> > > suggest that in that case ASLR would be left *on*.
> >
> > Yeah, sounds weird....
>
> Yes, this is just stupidity. Revised patch attached.
Heh, please push.
Thanks,
Corinna
> From 9ffce0d6124933cf16aee3ad006e32858fe0754a Mon Sep 17 00:00:00 2001
> From: Jon Turney <jon.turney@dronecode.org.uk>
> Date: Tue, 1 Nov 2022 16:52:57 +0000
> Subject: [PATCH] Cygwin: Improve FAQ on early breakpoint for ASLR
>
> gdb supports the 'disable-randomization' setting on Windows since [1]
> (included in gdb 13).
>
> https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=bcb9251f029da8dcf360a4f5acfa3b4211c87bb0;hp=8fea1a81c7d9279a6f91e49ebacfb61e0f8ce008
> ---
> winsup/doc/faq-programming.xml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
> index 7945b6b88..36d0a401f 100644
> --- a/winsup/doc/faq-programming.xml
> +++ b/winsup/doc/faq-programming.xml
> @@ -844,6 +844,12 @@ Guide here: <ulink url="https://cygwin.com/cygwin-ug-net/dll.html"/>.
> Note that the DllMain entrypoints for linked DLLs will have been executed
> before this breakpoint is hit.
> </para>
> +
> +<para>
> + (It may be necessary to use the <command>gdb</command> command <command>set
> + disable-randomization on</command> to turn off ASLR for the debugee to
> + prevent the base address getting randomized.)
> +</para>
> </answer></qandaentry>
>
> <qandaentry id="faq.programming.debug">
> --
> 2.38.1
>
next prev parent reply other threads:[~2022-11-04 13:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:04 Jon Turney
2022-11-03 18:22 ` Jeremy Drake
2022-11-04 10:34 ` Corinna Vinschen
2022-11-04 12:53 ` Jon Turney
2022-11-04 13:16 ` Corinna Vinschen [this message]
2022-11-04 15:29 ` Pedro Alves
2022-11-12 14:30 ` Jon Turney
2022-11-15 10:46 ` Corinna Vinschen
2022-11-28 13:00 ` Jon Turney
2022-11-28 14:41 ` Corinna Vinschen
2022-12-05 15:23 ` Johannes Schindelin
2022-12-11 13:54 ` Jon Turney
2022-12-11 14:45 ` Johannes Schindelin
2022-12-14 17:37 ` Jon Turney
2023-03-28 8:26 ` Johannes Schindelin
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=Y2UQvCw5NXNIYHTb@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).