Quote:
Originally Posted by prb28
I've to look what vasm and vlink docs say about this scenario. I don't know if including a ".s" file is support by the -linedebug option.
|
No, not yet. Sorry.
-linedebug is currently a Q&D solution in the hunk output module, which always puts the name of the main source file in the LINE debug header.
I already implemented a more sophisticated source file management for DWARF debug sections. So the information is theoretically available. I might have a look in improving -linedebug over the next days...