This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: How to disable GDB backtrace new behavior of including disassembly in backtrace ?
- From: Bernd Edlinger <bernd dot edlinger at hotmail dot de>
- To: William Tambe <tambewilliam at gmail dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Cc: Andrew Burgess <andrew dot burgess at embecosm dot com>
- Date: Wed, 25 Dec 2019 19:50:59 +0000
- Subject: Re: How to disable GDB backtrace new behavior of including disassembly in backtrace ?
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1LHlTVdOJBaJTQsKIeTyr0tN12gd+div4iinuHu7NXo=; b=EwnEHS2yJx6IooTGuI+XsdyTxDlk5enXe1KcYJApGwumraVsJyL1bYPCAQ/HA1WBltgafBUzEJWILar9sbKlwd87X3roPLZG4qCgtYF1N5qs3GzNWTUjEvEp42nJ06OmvTspAqu+075kfT4fgTyHjXaFCWulcwNXHgrNsoJslN5OhD6HdDXhhwC4ukmGOCBdgvg9twvIbXcvDW2C8mAewvtCTGokmMykBI2PIZ8EFe+A0ZfinWsYg8YbuuPhQl4G4z8XOFlF+6m7m75F00A6JNbHJwVzoCcjZo9R63EYyBoUFJXVJZtW91EobJZbWk5Ci/tI7FPnSbZNaYoLTXmlyQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=acKW/Fy4gheWh8KmGFeuL3arM7mYXNiCWwVLnw2FKER9X2q3GquzJpPoYbc2Spuw4f7Hu28ZIX5bOcUb1zKkSluigQJFrJeskduscmjO9HfnunNLOQX1Lwmqzr6jYmwaWAtELpT3zvygb/c1WD9MJLLqs4uYQgeDXbMn+yl53j+TPW3dfglKO0+l3b3b7/nn7SL4m72D2FSudqfkPVjq2Z2kWu/hpksdplS+vuus1Nz7Kfu547pCZqG4DOYysP9nUAuEynQwgxMzQSQ4A5PQYnMEKYYrEtuvkvy93vpe7asaD8gejd9gRgjIlPwLObvJjsAcEm823DLF/gT1uU7Q7w==
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=<optimized out>,
> cfs_rq=<optimized out>) at /linux/kernel/sched/fair.c:6844
> 0x0005ed38 <pick_next_task_fair+492>: 80 74 li8 %7, 0x4 # 4
> 0x0005ed3a <pick_next_task_fair+494>: b8 70 add %7, %sp
> 0x0005ed3c <pick_next_task_fair+496>: ea 37 ld32 %3, %7
> 0x0005ed3e <pick_next_task_fair+498>: c7 13 cpy %1, %3
> 0x0005ed40 <pick_next_task_fair+500>: 92 10 inc8 %1, 32 # 0x20
> => 0x0005ed42 <pick_next_task_fair+502>: ea 11 ld32 %1, %1
> 0x0005ed44 <pick_next_task_fair+504>: ea 50 ld32 %5, %sp
> 0x0005ed46 <pick_next_task_fair+506>: e0 d0 gip %sr
> 0x0005ed48 <pick_next_task_fair+508>: a2 d0 4e 00 00 00
> inc32 %sr, 78 # 0x4e
> 0x0005ed4e <pick_next_task_fair+514>: d1 1d jnz %1, %sr
> #1 pick_next_task_fair (rq=<optimized out>, prev=<optimized out>,
> rf=<optimized out>) 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=<optimized out>,
> cfs_rq=<optimized out>) at /linux/kernel/sched/fair.c:6844
> #1 pick_next_task_fair (rq=<optimized out>, prev=<optimized out>,
> rf=<optimized out>) 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 <andrew.burgess@embecosm.com>
Date: Fri Jun 14 23:43:00 2019 +0100
gdb: Don't allow annotations to influence what else GDB prints
Bernd.