On Fri, Feb 01, 2019 at 01:38:05PM -0800, Doug Anderson wrote: > Hi, Hi Doug,
> I was wondering if anyone out there has given any thought to > annotating the ARM64 IRQ handling in such a way that we could stack > crawl past el1_irq() when in gdb. > > I spent a bit of time on this a few months ago and documented all my > findings in: > > https://bugs.chromium.org/p/chromium/issues/detail?id=908721 There, the error from GDB is: Backtrace stopped: previous frame identical to this frame (corrupt stack?) ... is that misleading? ... or do we have some duplicate stack frame that we somewhow skip in the kernel unwinder? > I can copy and paste all the discussion from that bug here, but since > it's public hopefully folks can read the discussion / investigation > there. To put it briefly, though: I can stack crawl past "el1_irq" > with the normal linux stack crawl (which is what kdb uses) but I can't > crawl past "el1_irq" in gdb(). After talking to some of our tools > guys here I'm fairly certain that we could solve this with the right > CFI directives, but when I poked at it I wasn't able to figure out the > magic. AFAICT, we don't know why GDB is terminating early. Could we please figure that out first? e.g. by looking for the above message in the GDB sources. If we do need CFI annotations, I'd rather move that entry code to C first, to minimize how painful that is. I have an ongoing project [1] to do just that... Thanks, Mark. [1] https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/log/?h=arm64/entry-deasm _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
