diff options
| author | Lioncash <mathew1800@gmail.com> | 2019-01-26 21:19:04 -0500 |
|---|---|---|
| committer | Lioncash <mathew1800@gmail.com> | 2019-01-26 21:19:13 -0500 |
| commit | 7842536ddba1c816d6487c19b4c35b675996e54f (patch) | |
| tree | da848c70a7f68f488414df15b577e8ce49693d2b /src/core/hle/kernel/svc.cpp | |
| parent | 1f4ca1e841cd0b0427218d787efe10a3fa62df33 (diff) | |
kernel/svc: Log out uncaught C++ exceptions from svcBreak
Looking into the implementation of the C++ standard facilities that seem
to be within all modules, it appears that they use 7 as a break reason
to indicate an uncaught C++ exception.
This was primarily found via the third last function called within
Horizon's equivalent of libcxxabi's demangling_terminate_handler(),
which passes the value 0x80000007 to svcBreak.
Diffstat (limited to 'src/core/hle/kernel/svc.cpp')
| -rw-r--r-- | src/core/hle/kernel/svc.cpp | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/core/hle/kernel/svc.cpp b/src/core/hle/kernel/svc.cpp index 6588bd3b8a..7cfecb68cf 100644 --- a/src/core/hle/kernel/svc.cpp +++ b/src/core/hle/kernel/svc.cpp @@ -597,6 +597,7 @@ enum class BreakType : u32 { PostNROLoad = 4, PreNROUnload = 5, PostNROUnload = 6, + CppException = 7, }; struct BreakReason { @@ -669,6 +670,9 @@ static void Break(u32 reason, u64 info1, u64 info2) { "Signalling debugger, Unloaded an NRO at 0x{:016X} with size 0x{:016X}", info1, info2); break; + case BreakType::CppException: + LOG_CRITICAL(Debug_Emulated, "Signalling debugger. Uncaught C++ exception encountered."); + break; default: LOG_WARNING( Debug_Emulated, |