Ingo Rammer wrote: > One possible workaround should therefore be to create a dummy windows > executable (which just starts and immediately exists) and register this .exe > as the system's JIT debugger....
Another solution would be to launch the process with the DEBUG_PROCESS flag. Then just enter a very simple WaitForDebugEvent() loop and monitor for first-chance exceptions. If you get an access violation (code 0xC0000005), just tear down the process. When you get the process exit debug event, exit your loop. -- Steve Johnson =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
