From: Tom Tromey <tom@tromey.com>
To: cbiesinger@chromium.org
Cc: gdb-patches@sourceware.org, Christian Biesinger <cbiesinger@google.com>
Subject: Re: [PATCH 1/3] Support the NetBSD version of pthread_setname_np
Date: Fri, 24 Jan 2020 15:04:00 -0000 [thread overview]
Message-ID: <87lfpwj3s2.fsf@tromey.com> (raw)
In-Reply-To: <20200124141458.171392-2-cbiesinger@chromium.org> (cbiesinger@chromium.org's message of "Fri, 24 Jan 2020 15:14:56 +0100")
>>>>> ">" == cbiesinger <cbiesinger@chromium.org> writes:
>> From: Christian Biesinger <cbiesinger@google.com>
>> On NetBSD, pthread_setname_np takes a printf-style format string plus
>> one argument:
>> https://netbsd.gw.com/cgi-bin/man-cgi?pthread_setname_np++NetBSD-current
>> This patch makes thread-pool.c handle that.
>> gdbsupport/ChangeLog:
>> 2020-01-24 Christian Biesinger <cbiesinger@google.com>
>> * thread-pool.c (set_thread_name): Add an overload for the NetBSD
>> version of pthread_setname_np.
Thank you. This is ok.
Tom
next prev parent reply other threads:[~2020-01-24 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 14:15 [PATCH 0/3] Fix some ARM NetBSD compile errors cbiesinger
2020-01-24 14:15 ` [PATCH 1/3] Support the NetBSD version of pthread_setname_np cbiesinger
2020-01-24 14:59 ` Kamil Rytarowski
2020-01-24 15:04 ` Tom Tromey [this message]
2020-01-24 14:15 ` [PATCH 3/3] Make the class name in the definition match the declaration cbiesinger
2020-01-24 14:54 ` Kamil Rytarowski
2020-01-24 15:06 ` Tom Tromey
2020-01-24 15:49 ` Christian Biesinger via gdb-patches
2020-01-24 14:18 ` [PATCH 2/3] Define _KMEMUSER in arm-nbsd-nat.c cbiesinger
2020-01-24 14:22 ` [PATCH 2/3 v2] " cbiesinger
2020-01-24 14:32 ` Kamil Rytarowski
2020-01-24 14:34 ` Christian Biesinger via gdb-patches
2020-01-24 14:36 ` [PATCH v3 2/3] Define _KERNTYPES " cbiesinger
2020-01-24 15:04 ` Tom Tromey
2020-01-24 14:58 ` [PATCH 2/3 v2] Define _KMEMUSER " Christian Biesinger via gdb-patches
2020-01-24 15:36 ` Kamil Rytarowski
2020-01-24 15:37 ` Christian Biesinger via gdb-patches
2020-01-24 15:49 ` Kamil Rytarowski
2020-01-24 16:25 ` Christian Biesinger via gdb-patches
2020-01-24 16:45 ` Kamil Rytarowski
2020-01-27 21:28 ` Christian Biesinger via gdb-patches
2020-02-05 18:02 ` Christian Biesinger via gdb-patches
2020-02-06 13:25 ` Kamil Rytarowski
2020-02-06 13:19 ` Kamil Rytarowski
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=87lfpwj3s2.fsf@tromey.com \
--to=tom@tromey.com \
--cc=cbiesinger@chromium.org \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
/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