From a98056191d9664926b9f0b75e127ef1dbe41b332 Mon Sep 17 00:00:00 2001 From: Ivan Leo Murray-Smith Date: Mon, 19 Apr 2004 23:07:47 +0000 Subject: [PATCH] Use WINEDEBUG instead of --debugmsg. --- documentation/architecture.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/architecture.sgml b/documentation/architecture.sgml index 959f43c9a64..745a8ffbf4b 100644 --- a/documentation/architecture.sgml +++ b/documentation/architecture.sgml @@ -185,8 +185,8 @@ "emulation", and is what the applications expect anyway. - However, if the user specified --debugmsg - +relay, a thunk layer is inserted between the + However, if the user specified WINEDEBUG=+relay + , a thunk layer is inserted between the application imports and the Wine handlers; this layer is known as "relay" because all it does is print out the arguments/return values (by using the argument lists in the @@ -194,7 +194,7 @@ but it's invaluable for debugging misbehaving calls into Wine code. A similar mechanism also exists between Windows DLLs - Wine can optionally insert thunk layers between them, - by using --debugmsg +snoop, but since + by using WINEDEBUG=+snoop, but since no DLL descriptor information exists for non-Wine DLLs, this is less reliable and may lead to crashes.