stuff/suyu
stuff/suyu
1
0
Fork 0
mirror of https://git.suyu.dev/suyu/suyu.git synced 2024-11-30 23:36:26 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

kernel/svc: Log out uncaught C++ exceptions from svcBreak

Browse source 
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.
This commit is contained in:
Lioncash 2019-01-26 21:19:04 -05:00
parent 1f4ca1e841
commit 7842536ddb
No known key found for this signature in database
GPG key ID: 4E3C3CC1031BA9C7
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/core/hle/kernel/svc.cpp
View file

@ -597,6 +597,7 @@ enum class BreakType : u32 {
PostNROLoad = 4, PostNROLoad = 4,
PreNROUnload = 5, PreNROUnload = 5,
PostNROUnload = 6, PostNROUnload = 6,
CppException = 7,
}; };
struct BreakReason { 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, "Signalling debugger, Unloaded an NRO at 0x{:016X} with size 0x{:016X}", info1,
info2); info2);
break; break;
case BreakType::CppException:
LOG_CRITICAL(Debug_Emulated, "Signalling debugger. Uncaught C++ exception encountered.");
break;
default: default:
LOG_WARNING( LOG_WARNING(
Debug_Emulated, Debug_Emulated,