From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 0/8] Non-contiguous address range support
Date: Thu, 23 Aug 2018 16:16:00 -0000 [thread overview]
Message-ID: <ff312d1a-b20c-5116-52e4-196a8e391ed1@redhat.com> (raw)
In-Reply-To: <3adf2b7a4b075cefe791efabb0413383@polymtl.ca>
On 08/22/2018 07:22 PM, Simon Marchi wrote:
> Thanks, it looks good from my side. I'll let Pedro take a look at the test again.
Thanks. I have no further comments.
Pedro Alves
next prev parent reply other threads:[~2018-08-23 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 16:57 Kevin Buettner
2018-08-22 17:07 ` [PATCH v4 1/8] Add block range data structure for blocks with non-contiguous address ranges Kevin Buettner
2018-08-22 17:09 ` [PATCH v4 2/8] Record explicit block ranges from dwarf2read.c Kevin Buettner
2018-08-22 17:11 ` [PATCH v4 3/8] Add support for non-contiguous blocks to find_pc_partial_function Kevin Buettner
2018-08-22 17:14 ` [PATCH v4 4/8] Disassemble blocks with non-contiguous ranges Kevin Buettner
2018-08-22 17:16 ` [PATCH v4 5/8] Use BLOCK_ENTRY_PC in place of most uses of BLOCK_START Kevin Buettner
2018-08-22 17:18 ` [PATCH v4 6/8] Introduce find_function_entry_range_from_pc and use it in infrun.c Kevin Buettner
2018-08-22 17:19 ` [PATCH v4 7/8] Relocate block range start and end addresses Kevin Buettner
2018-08-22 17:20 ` [PATCH v4 8/8] Test case for functions with non-contiguous ranges Kevin Buettner
2018-08-22 18:22 ` [PATCH v4 0/8] Non-contiguous address range support Simon Marchi
2018-08-23 16:16 ` Pedro Alves [this message]
2018-08-23 23:31 ` Kevin Buettner
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=ff312d1a-b20c-5116-52e4-196a8e391ed1@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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).