From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25138 invoked by alias); 25 Feb 2011 11:44:26 -0000 Received: (qmail 25126 invoked by uid 22791); 25 Feb 2011 11:44:26 -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:44:22 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id C44E42BAEA8; Fri, 25 Feb 2011 06:44:20 -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 NX1CBEob2H8W; Fri, 25 Feb 2011 06:44:20 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 559352BAEA7; Fri, 25 Feb 2011 06:44:20 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 33755145A56; Fri, 25 Feb 2011 15:44:13 +0400 (RET) Date: Fri, 25 Feb 2011 11:49:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Jerome Guitton , gdb-patches@sourceware.org Subject: Re: [PATCH 18/18] document the new VxWorks port Message-ID: <20110225114413.GF2495@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> <83d3mgqr7y.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83d3mgqr7y.fsf@gnu.org> 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/msg00750.txt.bz2 > The result looks like a bad UI to me, and requires a separate > command. But if that's what VxWorks users prefer, fine. Does it still look bad to you after my explanation? IMO, I think it's OK. We have several modes: - single-task debugging: In that case, the task has only 1 thread. Everything else is irrelevant. - multi-task debugging: It's close to debugging a program. We only show the threads running in that program. - system-mode debugging (we debug the entire system as one giant program). In that case, we show all the threads. I think it makes sense. Perhaps, the confusion comes from the "info wtx threads" command itself, since it is not listing threads, but rather *tasks* (this is the technical term that WRS uses). We could change that command to "info wtx tasks"... But if we do, I'd to request that we also provide an alias to preserve compatibility with the current users. -- Joel