From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25945 invoked by alias); 27 Mar 2009 16:04:12 -0000 Received: (qmail 25467 invoked by uid 22791); 27 Mar 2009 16:04:07 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 Mar 2009 16:03:58 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n2RG3CX9003607; Fri, 27 Mar 2009 12:03:12 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n2RG34bp004641; Fri, 27 Mar 2009 12:03:04 -0400 Received: from opsy.redhat.com (vpn-14-142.rdu.redhat.com [10.11.14.142]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n2RG3Aqc019583; Fri, 27 Mar 2009 12:03:11 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id EECDD3780FB; Fri, 27 Mar 2009 10:03:08 -0600 (MDT) To: Eli Zaretskii Cc: Joel Brobecker , gdb-patches@sourceware.org Subject: Re: [RFA/doco] Document task-specific breakpoints References: <20090325214556.GD9472@adacore.com> <20090325220236.GF9472@adacore.com> <20090326223902.GL9472@adacore.com> <20090327153441.GP9472@adacore.com> From: Tom Tromey Reply-To: tromey@redhat.com Date: Fri, 27 Mar 2009 16:11:00 -0000 In-Reply-To: (Eli Zaretskii's message of "Fri\, 27 Mar 2009 18\:39\:11 +0300") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00629.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Joel> "Running" Joel> is another one of these states which just says that, from the Joel> point of view of the program, that this task is not waiting Joel> for an event, nor sleeping, nor waiting for a rendez-vous, etc. Joel> It's simply executing some code. Eli> But in fact, it isn't executing some code, it's stopped at a Eli> breakpoint, isn't it? If it is executing code, what code is that? It is displaying the state as the program sees it, not gdb's view of the task. Perhaps the documentation can explain why a stopped task might say "running". Tom