From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH v2 2/3] Use gdbarch for probe::get_argument_count
Date: Wed, 04 Sep 2019 18:00:00 -0000 [thread overview]
Message-ID: <87sgpcrlfa.fsf@redhat.com> (raw)
In-Reply-To: <87blw0t031.fsf@redhat.com> (Sergio Durigan Junior's message of "Wed, 04 Sep 2019 13:58:42 -0400")
On Wednesday, September 04 2019, I wrote:
> On Wednesday, August 21 2019, Alan Hayward wrote:
>
>> The probe function get_argument_count does not need a frame, only
>> the current gdbarch. Switch the code to pass gdbarch instead.
>> No functional changes.
>
> The patch looks good at first glance, but I'd like to apply it before
> approving. Unfortunately, it seems like your MUA has mangled the
> message (which is strange, because apparently you're using
> git-send-email):
>
> <https://sourceware.org/cgi-bin/get-raw-msg?listname=gdb-patches&date=2019-08&msgid=20190821155816.45504-3-alan.hayward%40arm.com>
>
> Can you resend it, please?
Ah, I see that the whole patch series has already been pushed. Sorry,
and please disregard my message.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-09-04 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 15:58 [PATCH v2 0/3] Fix stop-on-solib event failures Alan Hayward
2019-08-21 15:58 ` [PATCH v2 2/3] Use gdbarch for probe::get_argument_count Alan Hayward
2019-09-04 17:58 ` Sergio Durigan Junior
2019-09-04 18:00 ` Sergio Durigan Junior [this message]
2019-08-21 15:58 ` [PATCH v2 3/3] Check arguments for all probes before using them Alan Hayward
2019-08-21 15:58 ` [PATCH v2 1/3] Refactor svr4_create_solib_event_breakpoints Alan Hayward
2019-08-30 15:51 ` [PATCH v2 0/3] Fix stop-on-solib event failures Gary Benson
2019-09-02 13:20 ` Alan Hayward
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=87sgpcrlfa.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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