From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70098 invoked by alias); 25 Aug 2017 09:02:18 -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 52026 invoked by uid 89); 25 Aug 2017 09:02:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=H*r:15.0.1178.4, H*RU:15.0.1178.4, Hx-spam-relays-external:15.0.1178.4, splitted X-HELO: dgw.wapice.com Received: from dgw.wapice.com (HELO dgw.wapice.com) (81.209.51.126) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 25 Aug 2017 09:02:03 +0000 Received: from dgw.wapice.com (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 2BE9F1D8602_99FE789B for ; Fri, 25 Aug 2017 09:02:01 +0000 (GMT) Received: from EDB2.wapice.localdomain (unknown [10.0.4.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "edb2.wapice.localdomain", Issuer "wapice-AD0-CA" (not verified)) by dgw.wapice.com (Sophos Email Appliance) with ESMTPS id 2A5711D5963_99FE788F for ; Fri, 25 Aug 2017 09:02:00 +0000 (GMT) Received: from EDB3.wapice.localdomain (10.0.4.81) by EDB2.wapice.localdomain (10.0.4.80) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 25 Aug 2017 12:01:59 +0300 Received: from EDB3.wapice.localdomain ([fe80::2090:37a9:cd92:40d9]) by EDB3.wapice.localdomain ([fe80::2090:37a9:cd92:40d9%13]) with mapi id 15.00.1178.000; Fri, 25 Aug 2017 12:02:00 +0300 From: =?iso-8859-1?Q?Lassi_Niemist=F6?= To: "gdb@sourceware.org" Subject: Build root location affects debugging on PowerPC Date: Fri, 25 Aug 2017 09:02:00 -0000 Message-ID: <659baa98c7344fd2af55c359c1133681@EDB3.wapice.localdomain> x-ms-exchange-transport-fromentityheader: Hosted Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2017-08/txt/msg00068.txt.bz2 Hello, =20 I have a 32bit project, which is compiled both for x86 and the PowerPC MPC8= 309E processor with GCC 4.8.2 and -ggdb3. Debug symbols are splitted into a= separate debug file. I have a working setup for debugging both architectur= es using GDB 7.10.1 (custom build, --enable-target=3Dall), both for regular= and core dump analysis scenarios. =20 Recently I discovered a problem: whereas the x86 debugging works regardless= where my project's build root is located (typical scenario for core dump a= nalysis, another developer rebuilds the software to get matching symbols), = the powerpc debugging shows incorrect crash locations. Sure the source/buil= d paths will be tattooed to the debug information, which changes e.g. the .= o file content, but this should not affect debugging, should it? I have tes= ted that recompilation in the _same_ path does not cause the issue. =20 To investigate further, I tried to update to GDB 8.0, but hit a wall right = when trying to even open the core file: =20 "" (gdb) core warning: core file may not match specified executable file. [New LWP ****] Cannot access memory at address 0x3f4 Cannot access memory at address 0x3f0 gdbarch.c:3355: internal-error: int gdbarch_elf_make_msymbol_special_p(gdba= rch*): Assertion `gdbarch !=3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. "" =20 I will file a bug report about the 8.0 but does anyone have a clue what cou= ld be the problem with 7.10.1 and why specific to PowerPC? The problem is p= resent both for regular debugging (i.e. let it run and crash) and core dump= analysis. =20 -Lassi N.