Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: "J. Johnston" <jjohnstn@redhat.com>,
	Daniel Jacobowitz <drow@mvista.com>,
	gdb@sources.redhat.com
Subject: Re: gcore and nptl threads on linux
Date: Tue, 15 Apr 2003 21:43:00 -0000	[thread overview]
Message-ID: <3E9C7CE8.2010003@redhat.com> (raw)
In-Reply-To: <3E6DF316.8030605@redhat.com>

> Daniel Jacobowitz wrote:
> On Thu, Mar 06, 2003 at 03:17:33PM -0500, Andrew Cagney wrote:
> 
> You mean add them to the `struct thread_info' list?  Why not (ignoring technical realities for the moment :-)?
> 
> 
> How about a second list made up of thread_info structs for lwps?  That way, the current
> thread routines wouldn't have to constantly validate whether the list item was
> a thread or lwp.  This also would simplify the numbering system.  There
> could be equivalent lwp routines for accessing the list (e.g. iterate_over_lwps() ).
> 
> Something like that.  Is a new term needed though?
> 
> Have the thread and lwp code each have their own instance of a `struct tpid_info' list (struct context_info list)?
> 
> 
> Hmm, I'm not sure.  Let's take a little while to think about a better
> name?
> 
> 
> How about uow_info with uow standing for "unit of work"?

This came up once before:

http://sources.redhat.com/ml/gdb/2001-03/msg00126.html

shall baring major protest go with `struct ptid_info'?

Andrew



      reply	other threads:[~2003-04-15 21:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 23:40 J. Johnston
2003-03-05  0:52 ` Daniel Jacobowitz
2003-03-05 17:05   ` J. Johnston
2003-03-05 17:25     ` Daniel Jacobowitz
2003-03-06  0:56       ` Andrew Cagney
2003-03-06  1:04         ` Daniel Jacobowitz
2003-03-06  1:44           ` Andrew Cagney
2003-03-06  1:49             ` Daniel Jacobowitz
2003-03-06  1:27         ` J. Johnston
2003-03-06 20:17           ` Andrew Cagney
2003-03-06 20:21             ` Daniel Jacobowitz
2003-03-11  0:00               ` J. Johnston
2003-03-11 14:30                 ` Andrew Cagney
2003-04-15 21:43                   ` Andrew Cagney [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=3E9C7CE8.2010003@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jjohnstn@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