aboutsummaryrefslogtreecommitdiff
path: root/src/core/hle/kernel/svc.cpp
diff options
context:
space:
mode:
authorLioncash <mathew1800@gmail.com>2018-08-14 20:43:56 -0400
committerLioncash <mathew1800@gmail.com>2018-08-14 20:54:05 -0400
commit9f6aa5cda890987b5663f3f218f7e9482d800fc4 (patch)
tree6fdab05e0ea9d30dd48b353439f6a990a3f520cf /src/core/hle/kernel/svc.cpp
parentea8e6b93560a6a91f771a6770c7c39dc1725c26d (diff)
kernel/svc: Log svcBreak parameters
Given if we hit here all is lost, we should probably be logging the break reason code and associated information to distinguish between the causes.
Diffstat (limited to 'src/core/hle/kernel/svc.cpp')
-rw-r--r--src/core/hle/kernel/svc.cpp7
1 files changed, 5 insertions, 2 deletions
diff --git a/src/core/hle/kernel/svc.cpp b/src/core/hle/kernel/svc.cpp
index b24f409b30..6be5c474e7 100644
--- a/src/core/hle/kernel/svc.cpp
+++ b/src/core/hle/kernel/svc.cpp
@@ -250,8 +250,11 @@ static ResultCode ArbitrateUnlock(VAddr mutex_addr) {
}
/// Break program execution
-static void Break(u64 unk_0, u64 unk_1, u64 unk_2) {
- LOG_CRITICAL(Debug_Emulated, "Emulated program broke execution!");
+static void Break(u64 reason, u64 info1, u64 info2) {
+ LOG_CRITICAL(
+ Debug_Emulated,
+ "Emulated program broke execution! reason=0x{:016X}, info1=0x{:016X}, info2=0x{:016X}",
+ reason, info1, info2);
ASSERT(false);
}