From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24536 invoked by alias); 25 Feb 2011 10:26:39 -0000 Received: (qmail 24528 invoked by uid 22791); 25 Feb 2011 10:26:38 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=BAYES_00,TW_WT X-Spam-Check-By: sourceware.org Received: from mel.act-europe.fr (HELO mel.act-europe.fr) (194.98.77.210) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 Feb 2011 10:26:34 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-smtp.eu.adacore.com (Postfix) with ESMTP id 97028CB01EA; Fri, 25 Feb 2011 11:26:32 +0100 (CET) Received: from mel.act-europe.fr ([127.0.0.1]) by localhost (smtp.eu.adacore.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4+CPZPZM6eLc; Fri, 25 Feb 2011 11:26:24 +0100 (CET) Received: from province.act-europe.fr (province.act-europe.fr [10.10.0.214]) by mel.act-europe.fr (Postfix) with ESMTP id 18E6DCB0261; Fri, 25 Feb 2011 11:26:24 +0100 (CET) Received: by province.act-europe.fr (Postfix, from userid 560) id 100DA165BA1; Fri, 25 Feb 2011 11:26:24 +0100 (CET) Date: Fri, 25 Feb 2011 11:12:00 -0000 From: Jerome Guitton To: Eli Zaretskii Cc: Joel Brobecker , gdb-patches@sourceware.org Subject: Re: [PATCH 18/18] document the new VxWorks port Message-ID: <20110225102624.GB3211@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <838vx5rzf8.fsf@gnu.org> User-Agent: Mutt/1.5.17 (2007-11-01) 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/msg00745.txt.bz2 Thank you for your review. I'll let Joel give a complete response; I'll just answer one of your questions: > > +@kindex info wtx threads > > +@item info wtx threads > > Why a separate command? Isn't it possible to use "info threads"? "info threads" lists only the threads of the inferior, whereas "info wtx threads" lists all threads on target. Typically, to attach to one. It would be similar to "shell ps" on a native configuration. The reason why it is not called, say, "info wtx processes", is a particularity of VxWorks: most applications actually run on kernel space, and share the same memory area. So they are really threads, not processes.