From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5663 invoked by alias); 27 Mar 2009 15:35:01 -0000 Received: (qmail 5623 invoked by uid 22791); 27 Mar 2009 15:35:00 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_37 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 Mar 2009 15:34:53 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E93FB2BAAEC; Fri, 27 Mar 2009 11:34:50 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mTCTn42iglmi; Fri, 27 Mar 2009 11:34:50 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id B5EC82BAAE1; Fri, 27 Mar 2009 11:34:50 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 4A3A15BD21; Fri, 27 Mar 2009 08:34:41 -0700 (PDT) Date: Fri, 27 Mar 2009 15:39:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [RFA/doco] Document task-specific breakpoints Message-ID: <20090327153441.GP9472@adacore.com> References: <20090325214556.GD9472@adacore.com> <20090325220236.GF9472@adacore.com> <20090326223902.GL9472@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-03/txt/msg00623.txt.bz2 > > > > +(@value{GDBP}) info tasks > > > > + ID TID P-ID Pri State Name > > > > + 1 140022020 0 15 Child Activation Wait main_task > > > > +* 2 140045060 1 15 Running t2 > > > > > > "Running"? shouldn't it be stopped at breakpoint? > > > > In practice, yes, it is stopped. But this information is printed > > from the point of view of the runtime. To the runtime, task "t2" > > is running. > > Sorry, I don't understand. Can you elaborate? Sure. These states indicate what the tasks are currently doing. For instance "Child activation wait" above means that the task is waiting for its children to complete before it terminates (see the description of these state in the Manual). "Running" is another one of these states which just says that, from the point of view of the program, that this task is not waiting for an event, nor sleeping, nor waiting for a rendez-vous, etc. It's simply executing some code. > > Attached is a new version of the documentation patch: > > > > * gdb.texinfo (Ada Tasks): Add documentation about task-specific > > breakpoints. > > (Set Breaks): Add reference to thread-specific and task-specific > > breakpoints. > > OK, but I think the "running" part should be either fixed or > explained. I think that "Running" is fine and doesn't need fixing. So let me know if you'd like me to explain further. -- Joel