From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12158 invoked by alias); 15 Jun 2008 22:18:52 -0000 Received: (qmail 12149 invoked by uid 22791); 15 Jun 2008 22:18:52 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 15 Jun 2008 22:18:24 +0000 Received: from kahikatea.snap.net.nz (154.31.255.123.static.snap.net.nz [123.255.31.154]) by viper.snap.net.nz (Postfix) with ESMTP id 53ADB3DA63A; Mon, 16 Jun 2008 10:18:17 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 7FB7C8FC6D; Mon, 16 Jun 2008 10:18:04 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18517.38171.56057.31893@kahikatea.snap.net.nz> Date: Sun, 15 Jun 2008 22:31:00 -0000 To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: [patch:MI] Observer for thread-changed In-Reply-To: <200806152142.36083.ghost@cs.msu.su> References: <18509.7945.19078.399646@kahikatea.snap.net.nz> <20080614191328.GA11666@caradoc.them.org> <18516.16499.732319.353988@kahikatea.snap.net.nz> <200806152142.36083.ghost@cs.msu.su> X-Mailer: VM 7.19 under Emacs 22.2.50.2 X-IsSubscribed: yes 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: 2008-06/txt/msg00292.txt.bz2 > > I agree. I don't think that we should second guess what front ends will > > do. > > We should, or frontends will second guess what MI tells them. If the behaviour of MI is fully documented the frontend won't need to do guessing of any kind. > "Current > thread" is not a exact thing, and "current thread changed" is not an exact > thing either, so we should provide specific meaning that is most useful to > frontends, and opposed to providing a meaning that is most easy for gdb. I know that Pedro has a patch that might change things but what different meanings does "Current thread" have now. It seems pretty unambiguous to me: it's the value stored inferior_ptid and the thread that has a "*" next to it in the output of "info threads". -- Nick http://www.inet.net.nz/~nickrob