From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-62515-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 24293 invoked by alias); 27 Mar 2009 15:41:28 -0000
Received: (qmail 24285 invoked by uid 22791); 27 Mar 2009 15:41:27 -0000
X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout5.012.net.il (HELO mtaout5.012.net.il) (84.95.2.13)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 Mar 2009 15:41:19 +0000
Received: from conversion-daemon.i_mtaout5.012.net.il by i_mtaout5.012.net.il (HyperSendmail v2004.12) id <0KH600M008ML4700@i_mtaout5.012.net.il> for gdb-patches@sourceware.org; Fri, 27 Mar 2009 18:41:15 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([77.127.23.114]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KH600G2J8WQ5K81@i_mtaout5.012.net.il>; Fri, 27 Mar 2009 18:41:15 +0300 (IDT)
Date: Fri, 27 Mar 2009 15:50:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA/doco] Document task-specific breakpoints
In-reply-to: <20090327153441.GP9472@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <u8wmrm0v4.fsf@gnu.org>
References: <20090325214556.GD9472@adacore.com> <20090325220236.GF9472@adacore.com> <uwsacnc65.fsf@gnu.org> <20090326223902.GL9472@adacore.com> <uljqrmk0c.fsf@gnu.org> <20090327153441.GP9472@adacore.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-03/txt/msg00625.txt.bz2

> Date: Fri, 27 Mar 2009 08:34:41 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> "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.

But in fact, it isn't executing some code, it's stopped at a
breakpoint, isn't it?  If it is executing code, what code is that?

> > OK, but I think the "running" part should be either fixed or
> > explained.
> 
> I think that "Running" is fine and doesn't need fixing.

If I were the user looking at the "Running" status, I'd certainly
think that something is dead wrong with this task-specific breakpoint.