ReceiveTempSMS
/
Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Use WINEDEBUG instead of --debugmsg.

This commit is contained in:
Ivan Leo Murray-Smith 2004-04-19 23:07:47 +00:00 committed by Alexandre Julliard
parent f5da73f53e
commit a98056191d
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
documentation/architecture.sgml
View File

@ -185,8 +185,8 @@
"emulation", and is what the applications expect anyway. "emulation", and is what the applications expect anyway.
</para> </para>
<para> <para>
However, if the user specified <parameter>--debugmsg However, if the user specified <parameter>WINEDEBUG=+relay
+relay</parameter>, a thunk layer is inserted between the </parameter>, a thunk layer is inserted between the
application imports and the Wine handlers; this layer is application imports and the Wine handlers; this layer is
known as "relay" because all it does is print out the known as "relay" because all it does is print out the
arguments/return values (by using the argument lists in the arguments/return values (by using the argument lists in the
@ -194,7 +194,7 @@
but it's invaluable for debugging misbehaving calls into but it's invaluable for debugging misbehaving calls into
Wine code. A similar mechanism also exists between Windows Wine code. A similar mechanism also exists between Windows
DLLs - Wine can optionally insert thunk layers between them, DLLs - Wine can optionally insert thunk layers between them,
by using <parameter>--debugmsg +snoop</parameter>, but since by using <parameter>WINEDEBUG=+snoop</parameter>, but since
no DLL descriptor information exists for non-Wine DLLs, this no DLL descriptor information exists for non-Wine DLLs, this
is less reliable and may lead to crashes. is less reliable and may lead to crashes.
</para> </para>