From: John Baldwin <jhb@freebsd.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 2/7] Add a psuedosection for the NT_FREEBSD_THRMISC note.
Date: Tue, 19 Jan 2016 16:02:00 -0000 [thread overview]
Message-ID: <5879287.Jg2nJLmZ62@ralph.baldwin.cx> (raw)
In-Reply-To: <569E1244.6090407@redhat.com>
On Tuesday, January 19, 2016 10:39:00 AM Pedro Alves wrote:
> Typo in $subject. :-)
Ugh, I edited the commit to specifically fix that. Not sure how it was
still broken, but I've fixed it for real.
--
John Baldwin
next prev parent reply other threads:[~2016-01-19 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 18:38 [PATCH v4 0/7] Support kernel-backed user threads on FreeBSD John Baldwin
2016-01-18 18:38 ` [PATCH v4 3/7] Add support for extracting thread names from cores John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-18 18:38 ` [PATCH v4 2/7] Add a psuedosection for the NT_FREEBSD_THRMISC note John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-19 16:02 ` John Baldwin [this message]
2016-01-18 18:38 ` [PATCH v4 6/7] Add support for LWP-based threads on FreeBSD John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-18 18:38 ` [PATCH v4 7/7] Dump register notes for each thread when generating a FreeBSD core John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-18 18:38 ` [PATCH v4 1/7] Add support to readelf for reading FreeBSD ELF core notes John Baldwin
2016-01-18 18:47 ` [PATCH v4 5/7] Use LWP IDs with ptrace register requests on FreeBSD John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-18 18:47 ` [PATCH v4 4/7] Display per-thread information for threads in FreeBSD cores John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-19 16:02 ` John Baldwin
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=5879287.Jg2nJLmZ62@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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).