[llvm-dev] workaround to force LLD to make dwarf info sections mappable/loadable?
Andrew Kelley via llvm-dev
llvm-dev at lists.llvm.org
Mon Dec 3 14:30:03 PST 2018
On 12/3/18 5:24 PM, Andrew Kelley via llvm-dev wrote:
> The bottom line is that, there's no fundamental reason this cannot work;
> it is a quirk of conventions that is unnecessarily preventing the debug
> info from being mapped into memory.
One more thing - this project as it currently exists is a proof of
concept of how a bare bones embedded system executable running on bare
metal can still have the same advanced debugging capabilities as when
using, e.g. Linux. If the debug info can be directly mapped, and thus
eliminate a dependency on a file system or on a special bootloader, it's
a great demo.
I think this use case is valid.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the llvm-dev