From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [non-stop] 08/10 linux native support
Date: Thu, 10 Jul 2008 22:15:00 -0000 [thread overview]
Message-ID: <20080710221528.GA18013@caradoc.them.org> (raw)
In-Reply-To: <200807102251.28066.pedro@codesourcery.com>
On Thu, Jul 10, 2008 at 10:51:27PM +0100, Pedro Alves wrote:
> Then, this patch cleaned it up a bit further. Basically, it gets
> rid of the find_lwp_pid call in thread_db_find_new_threads. Instead
> I'm using ALL_LWPS, which is already exported. This gets rid
> of the find_lwp_pid -> linux_nat_lwp_pid rename throughout, and
> removes the need for thread_db_find_new_threads_1. I then
> reimported a couple of comments and cleanups that were on
> the last patch, since you had picked up the previous-to-last.
>
> Otherwise, the logic is the same.
>
> Regtested on x86_64-unknown-linux-gnu.
>
> OK?
Looks good to me.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-07-10 22:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 21:10 Pedro Alves
2008-06-25 21:17 ` Daniel Jacobowitz
2008-06-25 22:03 ` Pedro Alves
2008-06-25 22:12 ` Pedro Alves
2008-06-25 22:52 ` Daniel Jacobowitz
2008-06-25 23:08 ` Daniel Jacobowitz
2008-07-02 3:35 ` Pedro Alves
2008-07-07 18:20 ` Daniel Jacobowitz
2008-07-09 3:25 ` Michael Snyder
2008-07-09 3:47 ` Daniel Jacobowitz
2008-07-09 3:55 ` Michael Snyder
2008-07-09 7:55 ` Mark Kettenis
2008-07-09 7:56 ` Mark Kettenis
2008-07-10 15:28 ` Pedro Alves
2008-07-10 17:15 ` Daniel Jacobowitz
2008-07-10 18:01 ` Pedro Alves
2008-07-10 19:59 ` Daniel Jacobowitz
2008-07-10 21:51 ` Pedro Alves
2008-07-10 22:15 ` Daniel Jacobowitz [this message]
2008-07-10 23:01 ` 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=20080710221528.GA18013@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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