Show compiled debug info (DWARF, MDEBUG, ...)

[karas84]

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

[mkst]

Is this (not?) something that objdiff can solve? If someone were to write a parser for the debug sections?

[karas84]

Does objdiff support parsing debug symbols like, for example, CCC does? (asking because I honestly don't know).

My idea was to generate (at least for STAB) what CCC generates so that one can compare the current situation with what is in the symbols. An example would be something like this:

/* 0015c408 0000006c */ void SetETIM2File(/* s2 18 */ int addr)
{
	/* s0 16 */ int i;
	/* v0 2 */ int texnum;
	/* a1 5 */ int *offtop;
	/* 0x0(sp) */ SPRITE_DATA dummy;
}

I have this in my scratch and would like to know what the current code I'm compiling is doing. ATM I'm using a python script that downloads the scratch and feeds the current.o inside the zip to CCC's stdump. This works fine but an online version would be vastly more efficient.