From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1230 invoked by alias); 9 Oct 2003 15:40:44 -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 1220 invoked from network); 9 Oct 2003 15:40:44 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 9 Oct 2003 15:40:44 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 61B102B89; Thu, 9 Oct 2003 11:40:42 -0400 (EDT) Message-ID: <3F85817A.3040500@redhat.com> Date: Thu, 09 Oct 2003 15:40:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: A target has-a 1:N threads? References: <3F856BF9.5020708@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00155.txt.bz2 > Hello, > > At present GDB maintains a thread-db that contains all the "threads" known to GDB. The list is cross-target. That is, it can include both LWPs from the lower "process layer" and "threads" from the higher "thread layer". > > I think the currently implicit target <-> thread relationship should be made more explicit: > > - thread_info should point back at it's target > - a target should let you iterate over its "threads" > > This, I belive, will help clean-up the current tid:pid dance. A thread would always know its target and hence thread operations would always be applied at the correct level. Make that 0:N threads. I forgot the targets that don't have threads. Andrew