From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 4F2F43882100; Fri, 14 Jun 2024 19:49:04 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4F2F43882100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1718394544;
	bh=CUoLvg2oCCUPC/IjA0MtWW4Qj1XM/RUtHOKp3abnRWU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=SY4uqPtQnuIRAk5QxmCMO5DzCk2NNl0mQ+pPPSK0Cw4Dfm8PYO35H4HEeP4xBpIA6
	 kntK5YtdSSD0I3FNBLDHUz3xOeN5dbdc6VURJ1x5W7ZxaGeOMF9+8QXDTx0P14pEfw
	 mydedKNua/nOGGZ/WCmeF5HdN7uwI7t8J8PjbQ3M=
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31846] GDB fails to read build ID from debug file
Date: Fri, 14 Jun 2024 19:49:04 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simon.marchi at polymtl dot ca
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-31846-4717-eV1TCzRCf8@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31846-4717@http.sourceware.org/bugzilla/>
References: <bug-31846-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D31846

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simon.marchi at polymtl do=
t ca

--- Comment #3 from Simon Marchi <simon.marchi at polymtl dot ca> ---
I have no idea off hand for your actual problem.  But to debug GDB, configu=
re
(the top-level configure in binutils-gdb) with something like:

  $ ./configure CFLAGS=3D"-g3 -O0" CXXFLAGS=3D"-g3 -O0"
  $ make all-gdb -j$(nproc)  # the all-gdb target, in order to avoid buildi=
ng
the other tools

Then I usually cd in the gdb directory and use:

  $ ./gdb -nx -q --data-directory=3Ddata-directory <other args>

And you can debug gdb itself by doing:

  $ gdb --args ./gdb -nx -q --data-directory=3Ddata-directory <other args>

Debugging something like this should be relatively easy, since it's not
something timing dependent.  Break at the point the message is issued and w=
ork
your way up to see when code paths diverge.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=