public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jturney@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: Improve FAQ on early breakpoint for ASLR Date: Fri, 4 Nov 2022 15:11:36 +0000 (GMT) [thread overview] Message-ID: <20221104151136.D52CE3858286@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=8c68a8a4898f2607bf940716dbce5654f10c481b commit 8c68a8a4898f2607bf940716dbce5654f10c481b Author: Jon Turney <jon.turney@dronecode.org.uk> Date: Tue Nov 1 16:52:57 2022 +0000 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 Diff: --- 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">
reply other threads:[~2022-11-04 15:11 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221104151136.D52CE3858286@sourceware.org \ --to=jturney@sourceware.org \ --cc=cygwin-cvs@sourceware.org \ /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: linkBe 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).