From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-62527-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 31478 invoked by alias); 27 Mar 2009 17:49:43 -0000
Received: (qmail 31469 invoked by uid 22791); 27 Mar 2009 17:49:42 -0000
X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 	tests=AWL,BAYES_05,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; Fri, 27 Mar 2009 17:49:36 +0000
Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KH600I00EOPMX00@i_mtaout2.012.net.il> for gdb-patches@sourceware.org; Fri, 27 Mar 2009 20:49:31 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([77.127.23.114]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KH6006RIEUGI0W1@i_mtaout2.012.net.il>; Fri, 27 Mar 2009 20:49:29 +0300 (IDT)
Date: Fri, 27 Mar 2009 18:47:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA/doco] Document task-specific breakpoints
In-reply-to: <20090327161051.GU9472@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <u63hun9hu.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> <u8wmrm0v4.fsf@gnu.org> <20090327161051.GU9472@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/msg00637.txt.bz2

> Date: Fri, 27 Mar 2009 09:10:51 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> The problem is that I don't understand what it is that is so confusing
> to you.

What is confusing is this:

    (@value{GDBP}) info tasks
      ID       TID P-ID Pri State                 Name
       1 140022020   0   15 Child Activation Wait main_task
       2 140045060   1   15 Accept/Select Wait    t2
       3 140044840   1   15 Runnable              t1
    *  4 140056040   1   15 Running               t3

Task 2 is running, okay.

    (@value{GDBP}) b 15 task 2
    Breakpoint 5 at 0x120044cb0: file test_task_debug.adb, line 15.

Set a breakpoint for task 2.

    Breakpoint 5, test_task_debug () at test_task_debug.adb:15

Breakpoint is hit by task 2.

    (@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
       3 140044840   1   15 Runnable              t1
       4 140056040   1   15 Delay Sleep           t3

And task 2 is still running, even though it has hit the breakpoint.

Did I succeed in explaining what is confusing?  The task was running,
then it hit the breakpoint, but it is still "running".

If this is normal, at least remove the second "info tasks" and its
output from the example.