Is your feature request related to a problem? Please describe.
When decompiling code that has debug symbols, one would like the decompile it to match not only the original assembly but also it's generated debug info. An extra global variable could make the generated assembly match but that would generate a different debug info, hinting that the current solution is not 100% accurate.
Describe the solution you'd like
When generating the assembly, the generated debug info could also be displayed in a different tab next to the "Compilation" tab. This would need some kind of parsing of course. Something like CCC does for MDEBUG.
Describe alternatives you've considered
As of now, I compile the matched code on my machine (or use the one exported from decomp.me), extract and parse the debug info, and compare it with the original one.
Is your feature request related to a problem? Please describe. When decompiling code that has debug symbols, one would like the decompile it to match not only the original assembly but also it's generated debug info. An extra global variable could make the generated assembly match but that would generate a different debug info, hinting that the current solution is not 100% accurate.
Describe the solution you'd like When generating the assembly, the generated debug info could also be displayed in a different tab next to the "Compilation" tab. This would need some kind of parsing of course. Something like CCC does for MDEBUG.
Describe alternatives you've considered As of now, I compile the matched code on my machine (or use the one exported from decomp.me), extract and parse the debug info, and compare it with the original one.
Additional context None