From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: "J. Johnston" <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: gdb linux nptl patch 1
Date: Wed, 18 Jun 2003 23:11:00 -0000 [thread overview]
Message-ID: <20030618231149.GA469@nevyn.them.org> (raw)
In-Reply-To: <3EF0F0DF.2030802@redhat.com>
On Wed, Jun 18, 2003 at 04:08:15PM -0700, Michael Snyder wrote:
> J. Johnston wrote:
> [...]
> >This patch proposes adding a secondary list of thread_info structs that
> >keeps
> >track of the lwps. This list is kept distinct from the regular thread
> >list.
> >Since manipulating either list involves common operations, some base
> >operations
> >are added for generic thread_info list manipulation. The lin-lwp.c
> >layer is
> >changed to add and delete lwp thread_info structs to the lwp list when lwps
> >are added or deleted. The linux-proc.c code is changed to iterate
> >through the
> >lwp thread_info list rather than the thread list when creating the
> >pr_status
> >notes.
>
> Jeff, did you realize that lin-lwp.c already maintains a list of lwps?
> It even exports an iterator function. I think this list you're adding
> may be redundant.
It exports an iterator, but you can't usefully declare the iterator's
callback anywhere, since struct lwp_info is local to lin-lwp.c...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-18 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 0:19 J. Johnston
2003-06-05 18:35 ` J. Johnston
2003-06-17 15:28 ` Daniel Jacobowitz
2003-06-18 23:08 ` Michael Snyder
2003-06-18 23:11 ` Daniel Jacobowitz [this message]
2003-06-18 23:23 ` Michael Snyder
2003-06-18 23:27 ` Daniel Jacobowitz
2003-06-18 23:37 ` J. Johnston
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=20030618231149.GA469@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.com \
--cc=msnyder@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