From: Andrew Burgess <aburgess@redhat.com>
To: Tom Tromey <tom@tromey.com>,
Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/2] New test for find_pc_sect_line
Date: Fri, 19 May 2023 11:06:59 +0100 [thread overview]
Message-ID: <87v8go8wjg.fsf@redhat.com> (raw)
In-Reply-To: <87sfbtzh8v.fsf@tromey.com>
Tom Tromey <tom@tromey.com> writes:
>>>>>> "Andrew" == Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Andrew> Adds a new test to extend coverage of find_pc_sect_line, then adds
> Andrew> some asserts and safety checks to skip_prologue_using_sal.
>
> These both seem fine to me.
>
> Reviewed-By: Tom Tromey <tom@tromey.com>
Pushed.
Thanks,
Andrew
prev parent reply other threads:[~2023-05-19 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 8:37 Andrew Burgess
2023-05-18 8:37 ` [PATCH 1/2] gdb/testsuite: test for a function with no line table Andrew Burgess
2023-05-18 8:37 ` [PATCH 2/2] gdb: safety checks in skip_prologue_using_sal Andrew Burgess
2023-05-18 17:22 ` [PATCH 0/2] New test for find_pc_sect_line Tom Tromey
2023-05-19 10:06 ` Andrew Burgess [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=87v8go8wjg.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).