summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorGravatar Lioncash2018-08-14 20:43:56 -0400
committerGravatar Lioncash2018-08-14 20:54:05 -0400
commit25d71454d130bd5356030a54b9d62c58f05bdf47 (patch)
tree6fdab05e0ea9d30dd48b353439f6a990a3f520cf /src
parentMerge pull request #1055 from lioncash/init (diff)
downloadyuzu-25d71454d130bd5356030a54b9d62c58f05bdf47.tar.gz
yuzu-25d71454d130bd5356030a54b9d62c58f05bdf47.tar.xz
yuzu-25d71454d130bd5356030a54b9d62c58f05bdf47.zip
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')
-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 b24f409b3..6be5c474e 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) {
250} 250}
251 251
252/// Break program execution 252/// Break program execution
253static void Break(u64 unk_0, u64 unk_1, u64 unk_2) { 253static void Break(u64 reason, u64 info1, u64 info2) {
254 LOG_CRITICAL(Debug_Emulated, "Emulated program broke execution!"); 254 LOG_CRITICAL(
255 Debug_Emulated,
256 "Emulated program broke execution! reason=0x{:016X}, info1=0x{:016X}, info2=0x{:016X}",
257 reason, info1, info2);
255 ASSERT(false); 258 ASSERT(false);
256} 259}
257 260