From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24050 invoked by alias); 6 Mar 2003 20:17:37 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24038 invoked from network); 6 Mar 2003 20:17:37 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 6 Mar 2003 20:17:37 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 440FB2A9C; Thu, 6 Mar 2003 15:17:33 -0500 (EST) Message-ID: <3E67ACDD.6050205@redhat.com> Date: Thu, 06 Mar 2003 20:17:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "J. Johnston" , Daniel Jacobowitz Cc: gdb@sources.redhat.com Subject: Re: gcore and nptl threads on linux References: <3E653983.8010005@redhat.com> <20030305005218.GA9222@nevyn.them.org> <3E662E68.7010205@redhat.com> <20030305172511.GB4425@nevyn.them.org> <3E669CA1.2010201@redhat.com> <3E66A408.5020802@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00123.txt.bz2 >> 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)? Andrew