From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 42747 invoked by alias); 13 Dec 2019 19:48:52 -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 42738 invoked by uid 89); 13 Dec 2019 19:48:51 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=H*i:CAF8i9mMNk47, H*i:sk:kpNUUE6, H*f:CAF8i9mMNk47, H*MI:sk:kpNUUE6 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; Fri, 13 Dec 2019 19:48:49 +0000 Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 364841E573; Fri, 13 Dec 2019 14:48:47 -0500 (EST) Subject: Re: How to disable GDB backtrace new behavior of including disassembly in backtrace ? To: William Tambe , gdb@sourceware.org References: From: Simon Marchi Message-ID: <4bef00a7-eccd-a9cf-807d-504fa9bb1bb4@simark.ca> Date: Fri, 13 Dec 2019 19:48:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-12/txt/msg00019.txt.bz2 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 ? > Hi William, I have never seen this behavior. It's either a setting I have never encountered, or a Python script you have loaded that is providing this functionality (e.g. with a frame-filter). Are you able to reproduce this behavior with another program? If so, could you send a small reproducer (small source snippet to compile + GDB commands), we can try it and tell you if we see the same behavior. Simon