From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23275 invoked by alias); 19 Jun 2019 17:14:57 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 23265 invoked by uid 89); 19 Jun 2019 17:14:56 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: simark.ca Received: from simark.ca (HELO simark.ca) (158.69.221.121) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 19 Jun 2019 17:14:55 +0000 Received: from [172.16.0.120] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id D14621E7CE; Wed, 19 Jun 2019 13:14:52 -0400 (EDT) Subject: Re: MI commands with --thread (--frame?) do not preserve user selected thread / frame To: Jan Vrany , gdb@sourceware.org References: <5df1c9d79778a5d6703bba442031b5a1bbeda141.camel@fit.cvut.cz> <3b34a5e356a75454b6b7903048c0d62a409673d5.camel@fit.cvut.cz> <8b3e78c4-fd5d-598e-4dcf-712807102072@simark.ca> From: Simon Marchi Message-ID: Date: Wed, 19 Jun 2019 17:14:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-06/txt/msg00059.txt.bz2 On 2019-06-19 12:04 p.m., Jan Vrany wrote: > On Wed, 2019-06-19 at 11:54 -0400, Simon Marchi wrote: >> On 2019-06-19 11:10 a.m., Jan Vrany wrote: >>> On Wed, 2019-06-19 at 11:53 +0100, Jan Vrany wrote: >>>> Hi, >>>> >>>> I was debugging a multithreaded program and realized that using --thread option to >>>> verious MI command silently changes user selected thread - here's an example using >>>> separate UI and CLI chahhel (tested on commit 6f5601c4d0) >>>> >>>> >>> ... >>>> >>>> As you can see, there was no `frame`, `thread`, `-select-frame` or `-thread-select` command between >>>> first and second info thread / frame commands on CLI, yet the selected thread / frame changed (silently). >>>> >>>> Is this intended behavior? If so what's the rationale? >> >> No, this is indeed a known bug: >> >> https://sourceware.org/bugzilla/show_bug.cgi?id=20684 >> > > Ah, I see. > >>> >> So it seems to work (at least for a simple case, there might be some edge cases I don't recall). I >> think that the CLI and MI events about the thread change should not appear though, since the goal is >> to make it appear as if there is no user selection changes. > > I agree, the event should not be emitted. This was just a quick hack whether > it'd help in my case. If you think this is an acceptable way of "fixing" it, > I'm happy to improve this patch and submit. > > Jan Note to gdb@, the conversion continues here: https://sourceware.org/ml/gdb-patches/2019-06/msg00392.html Simon