Displaying 2 results from an estimated 2 matches for "ab0cc1f".
Did you mean:
ab0cc1fe
2018 Dec 03
2
workaround to force LLD to make dwarf info sections mappable/loadable?
Context: https://bugs.llvm.org/show_bug.cgi?id=39862
I'm trying to enable stack traces in an OS kernel. To do that the kernel
needs access to its own debug info. I have this in my linker script:
.debug_info : {
__debug_info_start = .;
KEEP(*(.debug_info))
__debug_info_end = .;
}
.debug_abbrev : {
__debug_abbrev_start = .;
2018 Dec 03
3
workaround to force LLD to make dwarf info sections mappable/loadable?
..._____________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181203/ab0cc1fe/attachment.html>