public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] Cygwin: Improve FAQ on early breakpoint for ASLR
Date: Sat, 12 Nov 2022 14:30:59 +0000	[thread overview]
Message-ID: <a2e01953-f6ef-cf08-f6e1-0c7632391ede@dronecode.org.uk> (raw)
In-Reply-To: <f2942e0e-ea5e-7ba9-8770-b422628dafad@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]

On 04/11/2022 15:29, Pedro Alves wrote:
> On 2022-11-04 12:53 p.m., Jon Turney wrote:
>> +<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>
>>   
> 
> Typo: debugee -> debuggee

Thanks for catching that.

Patch attached.

> Note that "on" is the default.

True.  But the API used by gdb to turn off ASLR isn't supported by some 
versions of Windows.

This sentence could be a lot more explicit about all the details here, 
but I'm just trying to be brief.

[-- Attachment #2: 0001-Cygwin-Fix-typo-in-FAQ.patch --]
[-- Type: text/plain, Size: 992 bytes --]

From be24c9b69e72648690a477fd2f15b0a9c6374713 Mon Sep 17 00:00:00 2001
From: Jon Turney <jon.turney@dronecode.org.uk>
Date: Sat, 12 Nov 2022 14:16:36 +0000
Subject: [PATCH] Cygwin: Fix typo in FAQ

The consonant in 'debug' is doubled in 'debuggee' just as it is in
'debugger'.

Fixes: 8c68a8a4
---
 winsup/doc/faq-programming.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
index 36d0a401f..89c309af2 100644
--- a/winsup/doc/faq-programming.xml
+++ b/winsup/doc/faq-programming.xml
@@ -847,7 +847,7 @@ Guide here: <ulink url="https://cygwin.com/cygwin-ug-net/dll.html"/>.
 
 <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
+  disable-randomization on</command> to turn off ASLR for the debuggee to
   prevent the base address getting randomized.)
 </para>
 </answer></qandaentry>
-- 
2.38.1


  reply	other threads:[~2022-11-12 14:31 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
2022-11-04 15:29       ` Pedro Alves
2022-11-12 14:30         ` Jon Turney [this message]
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=a2e01953-f6ef-cf08-f6e1-0c7632391ede@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).