From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A8A1E3858D1E; Tue, 25 Apr 2023 16:25:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A8A1E3858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1682439904; bh=T0Pwlca5I6towkh3c6M6ieGksImMc4Zfd23A3h8nL1c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=k/oWk8VngKH+CejjMLoVXsMGfg1ABLs4qvDxVtG+D6MOor/FNqU6cOPwc45FXcFoK FEln+NASz+Fqgea5AtA/YOKuEJlkC7P4i5cLoLZxUBH3zLkv/FJGWve0+yhRyINEdg btvB61RslIR7IVQVL7nPyVk4eppjhhZyZg8M12sU= From: "hikari at noyu dot me" To: gdb-prs@sourceware.org Subject: [Bug tdep/30386] Thumb flag on ARMv6 Mach-O ignored, symbols assumed to not be Thumb Date: Tue, 25 Apr 2023 16:25:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 13.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hikari at noyu dot me 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=3D30386 --- Comment #10 from hikari_no_yume --- Ah, but objdump for example does provide this symbol info to the disassembl= er, so objdump produces correct disassemblies in my testing with the same binary from earlier, which has a mix of Thumb and Arm functions. So this is specifically a gdb issue: - it doesn't provide symbol info to the disassembler, so the disassembler c= an't check for the Thumb flag - gdb also doesn't check for the Thumb flag itself, which would be useful f= or breakpoints etc It doesn't seem like there's a simple fix for this. I tried hacking BFD to = do value |=3D 1 when the flag is set, and that produced really weird and broken behaviour. A more involved fix does seem like it would be possible though. I'm not going to actively work on this more for now, but maybe I'll come ba= ck to it later. :) --=20 You are receiving this mail because: You are on the CC list for the bug.=