Hi Alexey,
On 03/13/12 20:59, Alexey Loukianov wrote:
Good day to all,
I've got a question, which is most probably should be addressed to Jacek Caban, concerning the proper way to debug and report about the problems with wine-gecko/mshtml implementation.
What I've got here is an app that crashes unless I install IE6 or IE7 (i.e. - native mshtml implementation) using winetricks. So, what should I do (what data to collect, what test to run) prior to firing up a new bug report to Bugzilla? Thanks in advance for hints.
Usually filing regular bug with terminal output is a good start. If terminal output is not enough, I (or anyone else looking at the bug) will request more logs. The usual interesting channels are mshtml,ieframe in this case, but occasionally also urlmon,wininet,tid or even trying debugging version of Gecko (although I would not advice debugging version of Gecko unless there is a reason, which I can't know without knowing more about the bug).
P.S. Another thing about wine-gecko vs. native dlls: in case one would try to install native VC++ 6.0 runtime and then try to run some app which imports mshtml - it would crash on wine-gecko trying to import non-exported function from msvcrt runtime. Is it considered a bug by Wine devs? Should I report it?
As Austin said, it's not a supported configuration.
Cheers, Jacek