Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Kamil Rytarowski <n54@gmx.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add support for NetBSD thread events (create, exit)
Date: Thu, 30 Apr 2020 14:28:25 -0400	[thread overview]
Message-ID: <f6032636-a016-f300-3759-66d56e69a341@simark.ca> (raw)
In-Reply-To: <trinity-a9d47dff-0aff-4cc6-b8bc-19887120bba8-1588255183159@3c-app-mailcom-bs10>

On 2020-04-30 9:59 a.m., Kamil Rytarowski wrote:
> Hello,
> 
> Please review.
> 
> commit 5446f5e7983ad9383e3bc0469327c94baa5e0587 (HEAD -> netbsd-3)
> Author: Kamil Rytarowski <n54@gmx.com>
> Date:   Thu Apr 30 16:13:33 2020 +0200
> 
>     Add support for NetBSD thread events (create, exit)
> 
>     Report LWP CREATE and LWP EXIT events and setup this on post_attach()
>     and post_startup_inferior().
> 
>     Stop reinitializing the list of recognized threads in update_thread_list().
> 
>     Handle LWP CREATE and EXIT events in nbsd_nat_target::wait().
> 
>     gdb/ChangeLog:
> 
>             * nbsd-nat.c (nbsd_enable_proc_events)
>             (nbsd_nat_target::post_startup_inferior): Add.
>             (nbsd_nat_target::post_attach): Call `nbsd_enable_proc_events'.
>             (nbsd_nat_target::update_thread_list): Rewrite.
>             (nbsd_nat_target::wait): Handle "PTRACE_LWP_EXIT" and
>             "PTRACE_LWP_CREATE".
>             * nbsd-nat.h (nbsd_nat_target::post_startup_inferior): Add.
> 

Check the tabs/spaces and alignment in:

	    printf_unfiltered (_("[%s exited]\n"),
                           target_pid_to_str (wptid).c_str ());

Otherwise, this LGTM, thanks.

Simon


      reply	other threads:[~2020-04-30 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 13:59 Kamil Rytarowski
2020-04-30 18:28 ` Simon Marchi [this message]

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=f6032636-a016-f300-3759-66d56e69a341@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=n54@gmx.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