On Tue, Feb 22, 2022 at 05:56:34PM +0000, Christophe Leroy wrote:
Ah! I was looking for {libgcc/,}crtsavres.S and not finding anything :-) Thanks for the clarification. That commit also removes the N_SO entries, which might be more crucial when trying to debug this code, might need some DWARF replacement (to find the source code to this).
I see that Linux's crtsavres.S (arch/powerpc/lib/crtsavres.S) has the following line:
(Huh, something failed in my searching apparently!)
.file "crtsavres.S"
Does this needs to be added to all .S files ? Is it enough to have the file name, isn't the path (relative to kernel source base ?) needed as well ?
I do not know. Try it out? When you break on a function in there (or single-step into it, etc.) do you get to see source code (for "list" etc.)? Or does the debugger refuse to break, or complain after breaking, or?
Segher