[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250214182439.gpavslsvgw4xy7sf@jpoimboe>
Date: Fri, 14 Feb 2025 10:24:39 -0800
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Puranjay Mohan <puranjay@...nel.org>
Cc: Song Liu <song@...nel.org>, Indu Bhagat <indu.bhagat@...cle.com>,
Weinan Liu <wnliu@...gle.com>, Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Mark Rutland <mark.rutland@....com>, roman.gushchin@...ux.dev,
Will Deacon <will@...nel.org>, Ian Rogers <irogers@...gle.com>,
linux-toolchains@...r.kernel.org, linux-kernel@...r.kernel.org,
live-patching@...r.kernel.org, joe.lawrence@...hat.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/8] unwind, arm64: add sframe unwinder for kernel
On Fri, Feb 14, 2025 at 08:56:45AM +0000, Puranjay Mohan wrote:
> I did this test and found the same issue as you (gdb assembly broken),
> but I can see this issue even without the inlining. I think GDB tried to
> load the debuginfo and that is somehow broken therefore it fails to
> disassemblt properly.
I had the same theory about the debuginfo, but I stripped debug sections
from that file and gdb still got confused.
Still, the symbol table looked normal, so the gdb issue might be
completely separate from the kernel runtime issues.
--
Josh
Powered by blists - more mailing lists