The Rotor exception handling should have this behavior on win32. On Windows, the Rotor portable exception handling is wrapper around the native win32 exception handling. Rotor exceptions are always raised as win32 exceptions - the win32 debugger will get first crack on these as usual. This is win32 specific, you won't get this behavior on FreeBSD.
All Rotor exceptions go through the emulation layer in the PAL, so the other option to get first crack on exceptions is to hook into PAL_ExceptionFilter in pal\unix\exception\exception.c. This is the way to go if you want your stuff to work on FreeBSD. You should be able to do the same hook for FreeBSD in SEHRaiseException in pal/unix/exception/exception.c. If you are interested only in managed exceptions, you may also check the managed debugging interfaces (clr\src\inc\cordebug.idl). A documentation for managed debugging interfaces can be found in .NET Framework SDK (FrameworkSDK\Tool Developers Guide\docs\DebugRef.doc). .NET Framework SDK is part of the Visual Studio .NET install, or it can be downloaded from msdn.microsoft.com. -Jan This posting is provided "AS IS" with no warranties, and confers no rights. -----Original Message----- From: Evgeny Vigdorchik [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 9:13 AM To: [EMAIL PROTECTED] Subject: [DOTNET-ROTOR] exception dispatching Hello, Sorry in advance if I'm going to ask something trivial... As MSDN says (article "Exception Dispatching") in win32 it is the debugger that is notified first (before any stack search is performed) of the debuggee exception. My question is: is this behavior supported by ROTOR, or possibly there is another efficient mechanism allowing the debugger prior access to debuggee's exceptions? Evgeny Vigdorchik St.Petersburg State University Institute of Information Systems
