[reactos] 01/01: [DRWTSN32] Recognize EXCEPTION_WINE_STUB (#2514)

[William Kent]

https://git.reactos.org/?p=reactos.git;a=commitdiff;h=3c48ec99924b5f4b5a58d8...

commit 3c48ec99924b5f4b5a58d862a7bd7e6e6f9b9362
Author:     William Kent [e-mail]
AuthorDate: Thu Apr 9 10:11:31 2020 -0400
Commit:     GitHub [e-mail]
CommitDate: Thu Apr 9 16:11:31 2020 +0200

[DRWTSN32] Recognize EXCEPTION_WINE_STUB (#2514)

DrWtsn32.exe recognizes several standard exception codes, and prints their names in the crash log. However, EXCEPTION_WINE_STUB is not in this list, and as such it is treated as an unknown error and printed as "--". Having this error code given a name at the start of the crash dump is useful, as it allows me to identify calls to unimplemented issues more readily.
---
 base/applications/drwtsn32/sysinfo.cpp | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/base/applications/drwtsn32/sysinfo.cpp b/base/applications/drwtsn32/sysinfo.cpp
index 84bc023a538..63576dccd08 100644
--- a/base/applications/drwtsn32/sysinfo.cpp
+++ b/base/applications/drwtsn32/sysinfo.cpp
@@ -9,6 +9,7 @@
 #include <udmihelp.h>
 #include <winreg.h>
 #include <reactos/buildno.h>
+#include <reactos/stubs.h>

static const char* Exception2Str(DWORD code)
 {
@@ -36,6 +37,7 @@ static const char* Exception2Str(DWORD code)
     case EXCEPTION_INVALID_DISPOSITION: return "EXCEPTION_INVALID_DISPOSITION";
     case EXCEPTION_GUARD_PAGE: return "EXCEPTION_GUARD_PAGE";
     case EXCEPTION_INVALID_HANDLE: return "EXCEPTION_INVALID_HANDLE";
+    case EXCEPTION_WINE_STUB: return "EXCEPTION_WINE_STUB";
     }

return "--";