From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111779 invoked by alias); 21 Oct 2017 14:13:29 -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 111760 invoked by uid 89); 21 Oct 2017 14:13:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:737 X-Spam-User: qpsmtpd, 2 recipients 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; Sat, 21 Oct 2017 14:13:27 +0000 Received: from [10.0.0.11] (cable-192.222.251.162.electronicbox.net [192.222.251.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 7E1971E4F3; Sat, 21 Oct 2017 10:13:25 -0400 (EDT) Subject: Re: Breakpoint commands in MI mode and "backtrace" To: Eli Zaretskii Cc: gdb@sourceware.org, gdb-patches@sourceware.org References: <8360bqt0im.fsf@gnu.org> <8a3d7153-7486-032f-aabc-6c3453f96459@simark.ca> <83shetsdg2.fsf@gnu.org> <83o9phs8zw.fsf@gnu.org> <83d15wsrvw.fsf@gnu.org> <83bmlgsqpm.fsf@gnu.org> <83vaj8c3fj.fsf@gnu.org> From: Simon Marchi Message-ID: Date: Sat, 21 Oct 2017 14:13:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <83vaj8c3fj.fsf@gnu.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-10/txt/msg00066.txt.bz2 On 2017-10-21 04:26 AM, Eli Zaretskii wrote: >> Cc: gdb@sourceware.org >> From: Simon Marchi >> Date: Mon, 9 Oct 2017 08:02:24 -0400 >> >> Anyhow, can you try this patch here? It changes the uiout manually instead of >> going through safe_execute_command. > > Since this worked for me, in GDB 8.0, can something similar be put in > the current master, so the next GDB release will have this bug fixed? > > Thanks. I'll look into it, but I'll try a slightly different patch. The one I sent previously sets and restores the interpreter at every executed command, which is inefficient. I'll try to set and restore only once at a higher level in the call stack. Simon