From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82235 invoked by alias); 25 Dec 2019 19:51:06 -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 82223 invoked by uid 89); 25 Dec 2019 19:51:05 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=influence, 83, William, william X-HELO: EUR04-HE1-obe.outbound.protection.outlook.com Received: from mail-oln040092073033.outbound.protection.outlook.com (HELO EUR04-HE1-obe.outbound.protection.outlook.com) (40.92.73.33) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 25 Dec 2019 19:51:03 +0000 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== 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-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none Received: from DB3EUR04FT047.eop-eur04.prod.protection.outlook.com (10.152.24.57) by DB3EUR04HT124.eop-eur04.prod.protection.outlook.com (10.152.24.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2581.11; Wed, 25 Dec 2019 19:51:00 +0000 Received: from AM0PR08MB3714.eurprd08.prod.outlook.com (10.152.24.57) by DB3EUR04FT047.mail.protection.outlook.com (10.152.25.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2581.11 via Frontend Transport; Wed, 25 Dec 2019 19:51:00 +0000 Received: from AM0PR08MB3714.eurprd08.prod.outlook.com ([fe80::8dd1:fb18:6271:f769]) by AM0PR08MB3714.eurprd08.prod.outlook.com ([fe80::8dd1:fb18:6271:f769%7]) with mapi id 15.20.2581.007; Wed, 25 Dec 2019 19:51:00 +0000 Received: from [192.168.1.101] (146.60.252.106) by FR2P281CA0008.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:a::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2581.11 via Frontend Transport; Wed, 25 Dec 2019 19:50:57 +0000 From: Bernd Edlinger To: William Tambe , "gdb-patches@sourceware.org" CC: Andrew Burgess Subject: Re: How to disable GDB backtrace new behavior of including disassembly in backtrace ? Date: Wed, 25 Dec 2019 19:51:00 -0000 Message-ID: x-microsoft-original-message-id: x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="Windows-1252" Content-ID: <5EB4EEA460442545835BB0D5878D5079@eurprd08.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SW-Source: 2019-12/txt/msg01007.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 ? >=20 > I have built GDB 8.3 and here is an example of output that I now see: >=20 > bt > #0 0x0005ed42 in set_next_entity (se=3D, > cfs_rq=3D) 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 > =3D> 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=3D, prev=3D, > rf=3D) at /linux/kernel/sched/fair.c:6844 >=20 > Using an earlier version of GDB would have just shown two lines > without disassembly; ie: >=20 > bt > #0 0x0005ed42 in set_next_entity (se=3D, > cfs_rq=3D) at /linux/kernel/sched/fair.c:6844 > #1 pick_next_task_fair (rq=3D, prev=3D, > rf=3D) at /linux/kernel/sched/fair.c:6844 >=20 > How can I restore the GDB old behavior when using backtrace ? >=20 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 Bernd.