Re: Separating Process and Debugger Debugmsg Output

[Eric Pouech]

> How do you solve this problem?

with today's CVS tree, not much I fear

my preferred solution would be to add some flags to CreateProcess
to ask for not passing some Wine elements from the parent process
to the child process (like -debug channels...) and use them
in the case of launching a debugger (would for any debugger not
only winedbg)

another hackish solution, not appliable as it is :
Index: win32/except.c
===================================================================
RCS file: /home/cvs/cvsroot/wine/wine/win32/except.c,v
retrieving revision 1.52
diff -u -r1.52 except.c
--- win32/except.c      10 Mar 2002 00:18:37 -0000      1.52
+++ win32/except.c      25 Apr 2002 18:45:06 -0000
@@ -274,6 +274,17 @@
     }

if (format) {
+        char    buffer[1024];
+
+        if (GetEnvironmentVariableA( "WINEOPTIONS", buffer,
sizeof(buffer) ) && buffer[0])
+        {
+            strncat( buffer, " --debugmsg -all", sizeof(buffer) );
+        }
+        else
+            strcpy( buffer, "--debugmsg -all" );
+        SetEnvironmentVariableA( "WINEOPTIONS", buffer );
+
+    /* check if any option remains */
         TRACE("Starting debugger (fmt=%s)\n", format);
         cmdline=HeapAlloc(GetProcessHeap(), 0, format_size+2*20);
         sprintf(cmdline, format, GetCurrentProcessId(), hEvent);

A+