From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4835 invoked by alias); 19 Feb 2003 16:05:25 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 4828 invoked from network); 19 Feb 2003 16:05:24 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by 172.16.49.205 with SMTP; 19 Feb 2003 16:05:24 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 4A52CD34B6; Wed, 19 Feb 2003 08:05:23 -0800 (PST) Date: Wed, 19 Feb 2003 16:05:00 -0000 From: Joel Brobecker To: Andrew Cagney Cc: gdb-patches@sources.redhat.com Subject: Re: Re-initializing a list after the control returns to gdb... Message-ID: <20030219160523.GM2105@gnat.com> References: <20030219020101.GI2105@gnat.com> <3E537DF0.50205@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E537DF0.50205@redhat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-02/txt/msg00407.txt.bz2 > A more higher level question. What exactly is the story behind > ada-task*. I glanced at the code and it looked very like a clone of the > existing thread code. Not quite: What happens is that the GNAT runtime maintains an array of Ada_Task_Control_Block. The ada-tasks module reads this array to build the list of tasks, and display the status information for each task. We then try to use the thread module to do the task switching. (We realize the code is a bit horrible, that's why we are trying to clean it up a bit. The question I asked was in fact for one of these cleanups. I can send my latest WIP version if yo are interested in the current state of this file). Does this answer your question? -- Joel