From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67863 invoked by alias); 16 Aug 2018 14:35:32 -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 67837 invoked by uid 89); 16 Aug 2018 14:35:31 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=HTo:D*io, andrey, Andrey X-HELO: mail-wr1-f45.google.com Received: from mail-wr1-f45.google.com (HELO mail-wr1-f45.google.com) (209.85.221.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 16 Aug 2018 14:35:30 +0000 Received: by mail-wr1-f45.google.com with SMTP id r16-v6so4353302wrt.11 for ; Thu, 16 Aug 2018 07:35:29 -0700 (PDT) Return-Path: Received: from ?IPv6:2a02:c7f:ae6a:ed00:4685:ff:fe66:9f4? ([2a02:c7f:ae6a:ed00:4685:ff:fe66:9f4]) by smtp.gmail.com with ESMTPSA id x82-v6sm2984097wmd.11.2018.08.16.07.35.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Aug 2018 07:35:26 -0700 (PDT) Subject: Re: gdb.execute(to_string=True) doesn't capture signal notice anymore To: gdb@sourceware.org, autkin@undo.io References: <20180815200855.GA24829@undo-autkin> From: Phil Muldoon Message-ID: <77540011-9d73-1388-ad6f-c0870c08be0b@redhat.com> Date: Thu, 16 Aug 2018 14:35:00 -0000 MIME-Version: 1.0 In-Reply-To: <20180815200855.GA24829@undo-autkin> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-08/txt/msg00032.txt.bz2 On 15/08/18 21:08, Andrey Utkin wrote: > Hi, > > We have some code which uses the fact of GDB 7.7 behaviour that if you > execute python code like > > s = gdb.execute("run", to_string=True) > > and, say, debuggee generates SIGTRAP, then result `s` includes the > string "Program received signal SIGTRAP, Trace/breakpoint trap." > > What we see is that since 7.12.1 or earlier, and until now, this is no > longer the case - this message is not captured but is only printed to > terminal. > > Before I dig into "fixing it", I want to know maintainers opinion - is > the current behaviour exactly what you like, or it's an unintended > regression and you'd prefer to preserve the old way? > This is a unintended regression unfortunately. The output of gdb.execute has been bitten by some ui-out reorganizing. https://sourceware.org/bugzilla/show_bug.cgi?id=21506 Cheers Phil