From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23333 invoked by alias); 25 Feb 2011 11:38:29 -0000 Received: (qmail 23325 invoked by uid 22791); 25 Feb 2011 11:38:29 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,TW_WT 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, 25 Feb 2011 11:38:24 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 41ED92BAE24; Fri, 25 Feb 2011 06:38:23 -0500 (EST) 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 zs3xtlV-B-EN; Fri, 25 Feb 2011 06:38:23 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id B1E012BAE1D; Fri, 25 Feb 2011 06:38:22 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 77A34145A56; Fri, 25 Feb 2011 15:38:15 +0400 (RET) Date: Fri, 25 Feb 2011 11:38:00 -0000 From: Joel Brobecker To: Jerome Guitton Cc: Eli Zaretskii , gdb-patches@sourceware.org Subject: Re: [PATCH 18/18] document the new VxWorks port Message-ID: <20110225113815.GE2495@adacore.com> References: <1298569763-18784-1-git-send-email-brobecker@adacore.com> <1298569763-18784-19-git-send-email-brobecker@adacore.com> <838vx5rzf8.fsf@gnu.org> <20110225102624.GB3211@adacore.com> <83ipw8qsfe.fsf@gnu.org> <20110225112647.GA2254@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110225112647.GA2254@adacore.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2011-02/txt/msg00748.txt.bz2 > > And what does "info threads" do on that target? > > It depends. In single-task mode, it displays only the thread being > debugged. In multi-tasks mode, it displays the list of threads that > have been created by a given kernel module. > > In both cases, "info threads" actually displays the threads that we > are debugging (e.g. that are stopped when a breakpoint is reached); > whereas "info wtx threads" displays any task running on kernel space > (even those that that are not being debugged). To expand a bit on what Jerome is saying, the reason we also do not want to show all the threads that are not being debugged, is that we do not want the user to attempt to switch to a thread that he is currently not debugging. -- Joel