From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH] Cygwin: Improve FAQ on early breakpoint for ASLR
Date: Thu, 3 Nov 2022 17:04:30 +0000 [thread overview]
Message-ID: <20221103170430.4448-1-jon.turney@dronecode.org.uk> (raw)
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
---
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..41cd5e423 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 off</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 reply other threads:[~2022-11-03 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:04 Jon Turney [this message]
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
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=20221103170430.4448-1-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).