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: Don't dump non-writable image regions
Date: Tue, 21 Jul 2020 14:20:32 +0000 (GMT)	[thread overview]
Message-ID: <20200721142032.7DFE9384B0C0@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=35227fec9781dd85ef30257f12b857d58dec1840

commit 35227fec9781dd85ef30257f12b857d58dec1840
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Sun Jul 5 14:42:59 2020 +0100

    Cygwin: Don't dump non-writable image regions
    
    After this, we will end up dumping memory regions where:
    
    - state is MEM_COMMIT (i.e. is not MEM_RESERVE or MEM_FREE), and
    -- type is MEM_PRIVATE and protection allows reads (i.e. not a guardpage), or
    -- type is MEM_IMAGE and protection allows writes
    
    Making this decision based on the current protection isn't 100% correct,
    because it may have been changed using VirtualProtect().  But we don't
    know how to determine if a region is shareable.
    
    (As a practical matter, anything which gets us the stack (MEM_PRIVATE)
    and .data/.bss (RW MEM_IMAGE) is going to be enough for 99% of cases)

Diff:
---
 winsup/utils/dumper.cc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/winsup/utils/dumper.cc b/winsup/utils/dumper.cc
index 2a0c66002..b96ee54cc 100644
--- a/winsup/utils/dumper.cc
+++ b/winsup/utils/dumper.cc
@@ -292,6 +292,12 @@ dumper::collect_memory_sections ()
       int skip_region_p = 0;
       const char *disposition = "dumped";
 
+      if ((mbi.Type & MEM_IMAGE) && !(mbi.Protect & (PAGE_EXECUTE_READWRITE | PAGE_READWRITE)))
+	{
+	  skip_region_p = 1;
+	  disposition = "skipped due to non-writeable MEM_IMAGE";
+	}
+
       if (mbi.Protect & PAGE_NOACCESS)
 	{
 	  skip_region_p = 1;


                 reply	other threads:[~2020-07-21 14:20 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=20200721142032.7DFE9384B0C0@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: 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).