From: Pedro Alves <palves@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 5/5] Test ability to access unwritten-to mmap data in core file
Date: Wed, 20 May 2020 17:46:38 +0100 [thread overview]
Message-ID: <a51f865e-0872-8e1b-10d4-90af87f5d5c0@redhat.com> (raw)
In-Reply-To: <20200513171155.645761-6-kevinb@redhat.com>
On 5/13/20 6:11 PM, Kevin Buettner via Gdb-patches wrote:
> gdb/testsuite/ChangeLog:
>
> PR corefiles/25631
> * gdb.base/corefile.exp (accessing anonymous, unwritten-to mmap data):
> New test.
> * gdb.base/coremaker.c (buf3): New global.
> (mmapdata): Add mmap call which uses MAP_ANONYMOUSE and MAP_PRIVATE
> flags.
OK.
Thanks,
Pedro Alves
prev parent reply other threads:[~2020-05-20 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 17:11 [PATCH v2 0/5] Fix BZ 25631 - core file memory access problem Kevin Buettner
2020-05-13 17:11 ` [PATCH v2 1/5] Remove hack for GDB which sets the section size to 0 Kevin Buettner
2020-05-13 17:11 ` [PATCH v2 2/5] Adjust corefile.exp test to show regression after bfd hack removal Kevin Buettner
2020-05-20 16:24 ` Pedro Alves
2020-05-13 17:11 ` [PATCH v2 3/5] section_table_xfer_memory: Replace section name with callback predicate Kevin Buettner
2020-05-20 16:33 ` Pedro Alves
2020-05-13 17:11 ` [PATCH v2 4/5] Provide access to non SEC_HAS_CONTENTS core file sections Kevin Buettner
2020-05-20 16:45 ` Pedro Alves
2020-05-21 7:50 ` Kevin Buettner
2020-05-21 12:40 ` Pedro Alves
2020-05-21 14:23 ` Pedro Alves
2020-05-21 15:09 ` Kevin Buettner
2020-05-21 16:28 ` Pedro Alves
2020-05-21 17:06 ` Pedro Alves
2020-05-13 17:11 ` [PATCH v2 5/5] Test ability to access unwritten-to mmap data in core file Kevin Buettner
2020-05-20 16:46 ` Pedro Alves [this message]
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=a51f865e-0872-8e1b-10d4-90af87f5d5c0@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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