From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64020 invoked by alias); 25 Dec 2019 20:19:44 -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 64005 invoked by uid 89); 25 Dec 2019 20:19:43 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Received:ac2, willingness, edlinger X-HELO: mail-lf1-f66.google.com Received: from mail-lf1-f66.google.com (HELO mail-lf1-f66.google.com) (209.85.167.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 25 Dec 2019 20:19:37 +0000 Received: by mail-lf1-f66.google.com with SMTP id v201so17233031lfa.11 for ; Wed, 25 Dec 2019 12:19:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Hq8axGsIDcBuwWhFhRa8kNfzJnty6JVCEm+Z11z/kNU=; b=pdiDe9ohCD7/dAm+yMaoh7+3PtsvkaXY9ErMlr3qUfq9W3A/hZ0yHPGzfWHJJafRaL r8/711zC8FfkKEAN7KRU2EtY5im4WoBb2l9oHZyrYbyXvKsMV6CzVZK/rw4QyuDoHj5Q Q/cDwu/oaEolAkpe2nDc9qztzajxZBOZuQZ90x4c1nj7k12hORGUnev7ZepjFGwldcAR WFbOLMSj3c6wg66aZ1O1oY0xenRCz3VM9FUV5+leZjM5VOWiFe9vPzcn5RVDmpMyN90h 01OxIoNwWtT5t54wmG0a2BAembK/rt+iFvKqYFK0uEurg3xyF+cqVD/4rcTvvFhGjjQT mS2A== MIME-Version: 1.0 References: In-Reply-To: From: William Tambe Date: Wed, 25 Dec 2019 20:19:00 -0000 Message-ID: Subject: Re: How to disable GDB backtrace new behavior of including disassembly in backtrace ? To: Bernd Edlinger Cc: "gdb-patches@sourceware.org" , Andrew Burgess Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-12/txt/msg01008.txt.bz2 On Wed, Dec 25, 2019 at 2:51 PM Bernd Edlinger wrote: > > 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" ? Yes. (gdb) show disassemble-next-line Debugger's willingness to use disassemble-next-line is on. > what is your setting of "show print frame-info" ? (gdb) show print frame-info Printing of frame information is "auto". > 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 > > If I use: (gdb) set disassemble-next-line auto or (gdb) set disassemble-next-line off then I no longer see this problem with the command backtrace. > > > Bernd. >