Luke Serné

Yeah, that fixes it. Thanks. It's no problem that these formats were not tested that well - unfortunately it seems the majority of people using APA are writing their reports...

I am personally not too happy with the way Tilburg University has decided to handle this. They have come up with [their own APA7 localisation](https://libguides.uvt.nl/apa-handleiding), which is subtly different from...

Are you sure `PowerPC:BE:64:VLEALT-32addr:default` is the correct processor language for this firmware image then? From this example, it seems like you should use `PowerPC:BE:64:VLE-32addr:default` instead. From looking online, it seems...

Note that the "constant appears on the left side of comparisons" part of this issue will be fixed if/when #4339 is merged

This bug occurs because the address of the jump table is not determined correctly. This happens because there is a mismatch between how the `segment` pcode op is implemented, and...

It seems like your sample is using protected mode instead of real mode. `CS` is set to `(0x10480478:4 >> 16:4) & 0xFFFF:4`, which is `0x1048`. This seems correct to me....

Thanks for the extra information. However, it seems like the debug xml generated by the decompiler does not contain all the relevant memory regions, because I get this error when...

The main difference between the example shared earlier and your sample is that the auto analysis in the `st.exe` sample automatically defines values for `CS` and `DS` at the start...

> It seems like some instructions are just not tied to any location in the decompiled source, though most times I can see exactly which source line should have been...

Related to #6002, which seems to report the same error, though the function arguments are correct in the example in issue #6002.