http://bugs.winehq.org/show_bug.cgi?id=9926
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #2 from Anastasius Focht focht@gmx.net 2007-11-02 02:50:18 --- Hello,
are you sure that this is a show stopper for SafeDisc 3.x? As I have already mentioned in http://bugs.winehq.org/show_bug.cgi?id=10273 SafeDisc's 2.x entry point code analyzer/disassembler (which might be present in 3.x too) probably mistreats the data exports as normal API code. Depending on pointer values at the point of analysis (runtime), invalid/unknown opcode sequences or invalid (cond) jump destinations might result from this. AFAIK the disassembler/tracer has it's own exception handler, catching any problematic tracer state.
Unfortunately I have no SafeDisc 3.x target to verify this (only guess)...
Regards