Question about --debugmsg +snoop
bon at elektron.ikp.physik.tu-darmstadt.de
Mon Jul 8 05:15:05 CDT 2002
>>>>> "Dmitry" == Dmitry Timoshkov <dmitry at baikal.ru> writes:
Dmitry> "Massimo" <max at veneto.com> wrote:
>> Is there a way to activate +snoop only for selected dll ???
Dmitry> Try +snoop=ole32.dll
Are you sure this still works after Alexandrs's restructuring of the debug
>> I think that would help me to find AutoCAD 2000 access violation on
>> startup, isolating the dll where it happens. As stated few msg
>> before, it starts up good with +snoop, but it crashes on very
>> beginning without +snoop.
Dmitry> Also try to disable smart arguments printing in
Dmitry> relay32/snoop.c,SNOOP_PrintArg() by commenting out
Dmitry> __TRY/__ENDTRY block of code.
Snooping fails when the DLL exports a variable and wine exchanges that
variable with a function call. The calling process accesses this function as
a variable, and writing to it crashes. The __TRY/__ENDTRY for argument
printing seems rather robust.
Uwe Bonnes bon at elektron.ikp.physik.tu-darmstadt.de
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
More information about the wine-devel