From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50108 invoked by alias); 25 Dec 2019 21:34:10 -0000 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 Received: (qmail 50100 invoked by uid 89); 25 Dec 2019 21:34:10 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-12.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*RU:209.85.128.65, HX-Spam-Relays-External:209.85.128.65, tomorrow X-HELO: mail-wm1-f65.google.com Received: from mail-wm1-f65.google.com (HELO mail-wm1-f65.google.com) (209.85.128.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 25 Dec 2019 21:34:08 +0000 Received: by mail-wm1-f65.google.com with SMTP id q9so3164039wmj.5 for ; Wed, 25 Dec 2019 13:34:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=embecosm.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=1oQfORNTprtjEvATQCWnyijit02gVDA3O44pEdLuOXs=; b=IPabh8zC2GbFfrycYnF9AJJ7jmg9Cl/FeiDX//WH3kAvew6cyX+9wZDj2ASF4N6OFj 8C6gblCKIHdstt/8pnre+LpPXPuzR02hs+i/WbflqFhv90RH66zNZ2/jTNZJPyPuehF8 XdwWGaR6Uu8/3DgXxhi+bM9I+04MlsJNc3xRed7q3C2TOa6RPfX9QOiVNRdqV9Z9rf4x ww8vhAqBL57Zue0CGT4p2UBN78aver36DiYWUw81Elbe2NPWva/EnFxiH2EM+QsaYV7A xbNmf8PSN6zmlS8zyx/4ZbQRkJ0VHbDBb7bOdiDe2HRDi0dTlWoq7ahfeNQF144QzVtG CPdA== Return-Path: Received: from localhost (host86-186-80-236.range86-186.btcentralplus.com. [86.186.80.236]) by smtp.gmail.com with ESMTPSA id u8sm6461562wmm.15.2019.12.25.13.34.05 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 25 Dec 2019 13:34:06 -0800 (PST) Date: Wed, 25 Dec 2019 21:34:00 -0000 From: Andrew Burgess To: Bernd Edlinger Cc: William Tambe , "gdb-patches@sourceware.org" Subject: Re: How to disable GDB backtrace new behavior of including disassembly in backtrace ? Message-ID: <20191225213404.GJ3865@embecosm.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Fortune: You will be successful in love. X-Editor: GNU Emacs [ http://www.gnu.org/software/emacs ] User-Agent: Mutt/1.9.2 (2017-12-15) X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg01010.txt.bz2 * Bernd Edlinger [2019-12-25 19:50:59 +0000]: > On 2019-12-13 7:09 a.m., William Tambe wrote: > > How to disable GDB backtrace new behavior of including disassembly in > > backtrace ? > > > > I have built GDB 8.3 and here is an example of output that I now see: > > > > bt > > #0 0x0005ed42 in set_next_entity (se=, > > cfs_rq=) at /linux/kernel/sched/fair.c:6844 > > 0x0005ed38 : 80 74 li8 %7, 0x4 # 4 > > 0x0005ed3a : b8 70 add %7, %sp > > 0x0005ed3c : ea 37 ld32 %3, %7 > > 0x0005ed3e : c7 13 cpy %1, %3 > > 0x0005ed40 : 92 10 inc8 %1, 32 # 0x20 > > => 0x0005ed42 : ea 11 ld32 %1, %1 > > 0x0005ed44 : ea 50 ld32 %5, %sp > > 0x0005ed46 : e0 d0 gip %sr > > 0x0005ed48 : a2 d0 4e 00 00 00 > > inc32 %sr, 78 # 0x4e > > 0x0005ed4e : d1 1d jnz %1, %sr > > #1 pick_next_task_fair (rq=, prev=, > > rf=) at /linux/kernel/sched/fair.c:6844 > > > > Using an earlier version of GDB would have just shown two lines > > without disassembly; ie: > > > > bt > > #0 0x0005ed42 in set_next_entity (se=, > > cfs_rq=) at /linux/kernel/sched/fair.c:6844 > > #1 pick_next_task_fair (rq=, prev=, > > rf=) at /linux/kernel/sched/fair.c:6844 > > > > How can I restore the GDB old behavior when using backtrace ? > > > > do you have "set disassemble-next-line on" ? > what is your setting of "show print frame-info" ? > I believe that previously this setting was only used in bt when > set print frame-info source-line / source-and-location > > Not sure if that was changed intentionally or not, it seems as if > this commit moved the do_gdb_disassemble out of the > "if (source_print && sal.symtab)" block, see: > > commit ec8e2b6d3051f0b4b2a8eee9917898e95046c62f > Author: Andrew Burgess > Date: Fri Jun 14 23:43:00 2019 +0100 > > gdb: Don't allow annotations to influence what else GDB prints I'm pretty sure I didn't mean for any change in that sort of behaviour. I'll try to take a look at this as soon as possible, that might be tomorrow, or possibly the day after. Thanks, Andrew