From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17395 invoked by alias); 31 Mar 2009 18:31:43 -0000 Received: (qmail 17264 invoked by uid 22791); 31 Mar 2009 18:31:36 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_37,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 31 Mar 2009 18:31:30 +0000 Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KHD00M00VF72Z00@i_mtaout2.012.net.il> for gdb-patches@sourceware.org; Tue, 31 Mar 2009 21:31:27 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.70.3.64]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KHD00GSQVGEWN20@i_mtaout2.012.net.il>; Tue, 31 Mar 2009 21:31:27 +0300 (IDT) Date: Tue, 31 Mar 2009 20:20:00 -0000 From: Eli Zaretskii Subject: Re: [RFA/doco] Document task-specific breakpoints In-reply-to: <20090331165513.GE9472@adacore.com> To: Joel Brobecker Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <20090325214556.GD9472@adacore.com> <20090325220236.GF9472@adacore.com> <20090331165513.GE9472@adacore.com> X-IsSubscribed: yes 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/msg00707.txt.bz2 > Date: Tue, 31 Mar 2009 09:55:13 -0700 > From: Joel Brobecker > > > 2009-03-25 Joel Brobecker > > > > * gdb.texinfo (Ada Tasks): Add documentation about task-specific > > breakpoints. > > I checked this patch in, with "Running" changed to "Runnable". > For the record, here is the final patch. Thanks. I wonder: would it make sense to add to this text elsewhere in the manual: @item Runnable The task is not blocked for any reason known to Ada. (It may be waiting for a mutex, though.) It is conceptually "executing" in normal mode. something that mentions the possibility that the task could be stopped at a breakpoint, not only waiting for a mutex?