http://bugs.winehq.org/show_bug.cgi?id=44827
--- Comment #22 from Armonius manicat@outlook.com --- @Bernhard(In reply to Bernhard Übelacker from comment #21)
Created attachment 79563 [details] notes of a debugging attempt
Looks like FL64.exe and ilbridge.exe synchronize their communication via events "{...}1_0_reader_evt_signal" and "{...}1_2_writer_evt_reader".
Because of that many threads and events, and at some places it waits for multiple events, I cannot point to something specific missing.
Because of the "TMethodImplementationIntercept" showing up in backtraces, FL64.exe and its Dlls seem to be written in Delphi.
DELPHI!!!! that explains it... i couldnt understand these VMT tables.. I spent 4 days just reading them up... maybe i can use the delphi helper plugin to parse these in IDA... I think the FL64.exe doesnt use delphi though... whoa I got to say i dont get backtraces as clean as you do... you used lldb? how do you configure that with wine? Thank you for your effort sir. I have much to learn from your notes.... I want to see if i can check each handle and see where each is coming from the moment it is freezing, but i can barely debug it in IDA via WINE. I need ScyllaHide to hook the anti-debugging functions but the version of ScyllaHide that has been released doesnt support my version of IDA.