Another observation - in DC3's symbols.txt, I have this entry:
?ReadEndian@BinStream@@QAAXPAXH@Z = .text:0x827DE458; // type:function size:0x40 scope:global
but despite being size 0x40, objdiff shows extra bytes that come after 0x40 in the .obj:
I have noticed that adding an except_data object below, like so:
?ReadEndian@BinStream@@QAAXPAXH@Z = .text:0x827DE458; // type:function size:0x40 scope:global
except_data_827DE4A0 = .text:0x827DE498; // type:object size:0x8 scope:global
fixes the objdiff view.
When making a scratch using pre-0.5.0 jeff (https://decomp.me/scratch/3bBwh) and 0.5.0 jeff (https://decomp.me/scratch/7PU2x), I'm seeing the extra bytes still end up after the function body. I'm wondering if objdiff can filter out those extra bytes without the need for an exception_data object, as I would like to remove those from my symbols.txt going forward.
Another observation - in DC3's symbols.txt, I have this entry:
?ReadEndian@BinStream@@QAAXPAXH@Z = .text:0x827DE458; // type:function size:0x40 scope:globalbut despite being size 0x40, objdiff shows extra bytes that come after 0x40 in the .obj:
I have noticed that adding an except_data object below, like so:
fixes the objdiff view.
When making a scratch using pre-0.5.0 jeff (https://decomp.me/scratch/3bBwh) and 0.5.0 jeff (https://decomp.me/scratch/7PU2x), I'm seeing the extra bytes still end up after the function body. I'm wondering if objdiff can filter out those extra bytes without the need for an exception_data object, as I would like to remove those from my symbols.txt going forward.