From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@freebsd.org>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH v2 3/6] Display per-thread information for threads in FreeBSD cores.
Date: Mon, 18 Jan 2016 17:13:00 -0000 [thread overview]
Message-ID: <569D1D40.6070809@redhat.com> (raw)
In-Reply-To: <1701896.llh381Sx0a@ralph.baldwin.cx>
On 01/18/2016 05:05 PM, John Baldwin wrote:
> Alternatively, would it be best if the core target defined a to_thread_name
> method that invoked a new gdbarch method (gdbarch_core_thread_name or the
> like) to fetch the thread name?
Yes, that's the right way to go.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-01-18 17:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 21:46 [PATCH v2 0/6] Support kernel-backed user threads on FreeBSD John Baldwin
2016-01-13 21:46 ` [PATCH v2 6/6] Dump register notes for each thread when generating a FreeBSD core John Baldwin
2016-01-14 15:34 ` Pedro Alves
2016-01-13 21:46 ` [PATCH v2 3/6] Display per-thread information for threads in FreeBSD cores John Baldwin
2016-01-14 15:03 ` Pedro Alves
2016-01-15 20:23 ` John Baldwin
2016-01-18 12:27 ` Pedro Alves
2016-01-18 17:06 ` John Baldwin
2016-01-18 17:13 ` Pedro Alves [this message]
2016-01-13 21:46 ` [PATCH v2 2/6] Add a psuedosection for the NT_FREEBSD_THRMISC note John Baldwin
2016-01-14 5:30 ` Alan Modra
2016-01-13 21:46 ` [PATCH v2 1/6] Add support to readelf for reading FreeBSD ELF core notes John Baldwin
2016-01-14 5:30 ` Alan Modra
2016-01-14 5:40 ` John Baldwin
2016-01-13 21:52 ` [PATCH v2 4/6] Use LWP IDs with ptrace register requests on FreeBSD John Baldwin
2016-01-14 15:07 ` Pedro Alves
2016-01-15 20:23 ` John Baldwin
2016-01-15 21:41 ` Pedro Alves
2016-01-15 23:54 ` John Baldwin
2016-01-16 14:39 ` Pedro Alves
2016-01-16 19:17 ` John Baldwin
2016-01-13 21:52 ` [PATCH v2 5/6] Add support for LWP-based threads " John Baldwin
2016-01-14 15:29 ` Pedro Alves
2016-01-15 23:54 ` John Baldwin
2016-01-16 14:47 ` Pedro Alves
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=569D1D40.6070809@redhat.com \
--to=palves@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).