From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH v2 3/6] Display per-thread information for threads in FreeBSD cores.
Date: Thu, 14 Jan 2016 15:03:00 -0000 [thread overview]
Message-ID: <5697B8D6.9010301@redhat.com> (raw)
In-Reply-To: <1452721551-657-4-git-send-email-jhb@FreeBSD.org>
On 01/13/2016 09:45 PM, John Baldwin wrote:
> Display the LWP ID of each thread in a FreeBSD core. Extract thread names
> from the per-thread THRMISC note.
>
> gdb/ChangeLog:
>
> * fbsd_tdep.c (fbsd_core_pid_to_str): New function.
> (fbsd_init_abi): Add "core_pid_to_str" gdbarch method.
> ---
> gdb/ChangeLog | 5 +++++
> gdb/fbsd-tdep.c | 41 +++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 46 insertions(+)
>
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index 471d02b..93760ba 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,3 +1,8 @@
> +2016-01-09 John Baldwin <jhb@FreeBSD.org>
> +
> + * fbsd_tdep.c (fbsd_core_pid_to_str): New function.
> + (fbsd_init_abi): Add "core_pid_to_str" gdbarch method.
> +
> 2016-01-08 Yao Qi <yao.qi@linaro.org>
>
> * extension.c: Include target.h.
> diff --git a/gdb/fbsd-tdep.c b/gdb/fbsd-tdep.c
> index 0ef94d6..6851cc1 100644
> --- a/gdb/fbsd-tdep.c
> +++ b/gdb/fbsd-tdep.c
> @@ -28,6 +28,46 @@
> #include "fbsd-tdep.h"
>
>
> +/* This is how we want PTIDs from core files to be printed. */
> +
> +static char *
> +fbsd_core_pid_to_str (struct gdbarch *gdbarch, ptid_t ptid)
> +{
> + static char buf[80], name[64];
This static "name" buffer appears unused, and then masked
by the "name" pointer below.
> + struct bfd_section *section;
> + bfd_size_type size;
> + char sectionstr[32];
> +
> + if (ptid_get_lwp (ptid) != 0)
> + {
> + snprintf (sectionstr, sizeof sectionstr, ".thrmisc/%ld",
> + ptid_get_lwp (ptid));
xsnprintf.
> + section = bfd_get_section_by_name (core_bfd, sectionstr);
> + if (section != NULL)
> + {
> + char *name;
> +
> + size = bfd_section_size (core_bfd, section);
> + name = alloca (size + 1);
> + if (bfd_get_section_contents (core_bfd, section, name, (file_ptr) 0,
> + size) && name[0] != '\0')
This indentation / line break reads unusual to me. I think breaking
before the && would be clearer:
if (bfd_get_section_contents (core_bfd, section, name,
(file_ptr) 0, size)
&& name[0] != '\0')
Guess this should check size > 0 as well, otherwise name[0] contains
garbage.
> + {
> + name[size] = '\0';
> + if (strcmp(name, elf_tdata (core_bfd)->core->program) != 0)
Missing space after strcmp.
Is this ".thrmisc" section documented somewhere? Could you add a
small comment on what this entry you're skipping means?
> + {
> + snprintf (buf, sizeof buf, "LWP %ld \"%s\"",
> + ptid_get_lwp (ptid), name);
xsnprintf.
> + return buf;
> + }
> + }
> + }
> + snprintf (buf, sizeof buf, "LWP %ld", ptid_get_lwp (ptid));
xsnprintf.
> + return buf;
> + }
> +
> + return normal_pid_to_str (ptid);
> +}
> +
> static int
> find_signalled_thread (struct thread_info *info, void *data)
> {
> @@ -132,5 +172,6 @@ fbsd_make_corefile_notes (struct gdbarch *gdbarch, bfd *obfd, int *note_size)
> void
> fbsd_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
> {
> + set_gdbarch_core_pid_to_str (gdbarch, fbsd_core_pid_to_str);
> set_gdbarch_make_corefile_notes (gdbarch, fbsd_make_corefile_notes);
> }
>
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-01-14 15:03 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 3/6] Display per-thread information for threads in FreeBSD cores John Baldwin
2016-01-14 15:03 ` Pedro Alves [this message]
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
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 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=5697B8D6.9010301@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).