From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 683813858D26; Sat, 22 Feb 2025 05:09:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 683813858D26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1740200953; bh=jgPgRZZwgV9LBgAoDSoaMIUUzqLC2uu4oq/2ZvrGKMY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AeRuF+0bDDsaMccUQ3ucUs2jRcqbMFHPDbRnE7cvilXFnZacgtHiJYih6rLSvyg0X YvssZFyprw0y7GDHgX9IgXyBJ2d1xErn/oZ9JaO4K0LMLS0lJThO2tlkEiIqTCiaRX VcN8ZCqA9YyBqaZt19+PUchXriqgQmFyv3v56PAU= From: "pixel@nobis-crew.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/32658] GDB sometimes fails parsing debug information Date: Sat, 22 Feb 2025 05:09:12 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pixel@nobis-crew.org 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: Message-ID: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D32658 --- Comment #2 from Nicolas Noble --- You shouldn't need to run it, really, to see the problem. Just loading the binary into gdb and doing info line *0x800334b0 for instance is enough. But if you really want to run this binary however, this is a PlayStation 1 software, which you'd need to run within an emulator with gdb support, and = that could potentially be more involved than using qemu. However, you can check = the one I'm the maintainer of here: https://github.com/grumpycoders/pcsx-redux/?tab=3Dreadme-ov-file#where Starting the emulator with the gdb server enabled is as simple as running t= his command: $ ./PCSX-Redux.appimage -stdout -interpreter -debugger -gdb=20 Then, from gdb itself: $ gdb test-gdb.elf (gdb) target remote localhost:3333 (gdb) monitor reset shellhalt (gdb) load test-gdb.elf (gdb) cont It'll display a lot of debugging information on stdout before eventually triggering a breakpoint. --=20 You are receiving this mail because: You are on the CC list for the bug.=