From: Carlos O'Donell <carlos@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] libthread_db initialization changes related to upcoming glibc-2.34
Date: Fri, 11 Jun 2021 22:58:06 -0400 [thread overview]
Message-ID: <30ace98c-5048-8d2c-beed-eca83eea1d2c@redhat.com> (raw)
In-Reply-To: <20210611152100.210e3399@f33-m1.lan>
On 6/11/21 6:21 PM, Kevin Buettner wrote:
> After making changes requested by Simon, I've pushed this
> series.
>
> Thanks to both Carlos and Simon for the quick reviews.
Thank you Kevin and Simon for prioritizing the debug experience
of GNU Toolchain developers :-)
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-06-12 2:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 17:26 Kevin Buettner
2021-06-10 17:26 ` [PATCH 1/4] " Kevin Buettner
2021-06-11 19:10 ` Simon Marchi
2021-06-11 21:24 ` Kevin Buettner
2021-06-10 17:26 ` [PATCH 2/4] testsuite/glib-2.34: Match/consume optional libthread_db related output Kevin Buettner
2021-06-11 19:13 ` Simon Marchi
2021-06-10 17:26 ` [PATCH 3/4] print-symbol-loading.exp: Allow libc symbols to be already loaded Kevin Buettner
2021-06-11 19:22 ` Simon Marchi
2021-06-11 19:33 ` Kevin Buettner
2021-06-11 21:05 ` Kevin Buettner
2021-06-10 17:26 ` [PATCH 4/4] mi-sym-info.exp: Increase timeout for 114-symbol-info-functions Kevin Buettner
2021-06-11 20:11 ` Simon Marchi
2021-06-11 21:07 ` Kevin Buettner
2021-06-11 22:21 ` [PATCH 0/4] libthread_db initialization changes related to upcoming glibc-2.34 Kevin Buettner
2021-06-12 2:58 ` Carlos O'Donell [this message]
2021-06-11 16:35 Carlos O'Donell
2021-06-11 17:08 ` Carlos O'Donell
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=30ace98c-5048-8d2c-beed-eca83eea1d2c@redhat.com \
--to=carlos@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).