Fatal services: Difference between revisions

From Nintendo Switch Brew
Jump to navigation Jump to search
No edit summary
No edit summary
Line 16: Line 16:
Takes an input u64 errorcode and an unknown u64(TID maybe?). It also takes a type-0x15 error buffer and a pid-descriptor. The error buffer contains a stack trace.  
Takes an input u64 errorcode and an unknown u64(TID maybe?). It also takes a type-0x15 error buffer and a pid-descriptor. The error buffer contains a stack trace.  
The stack trace address count is stored at errorbuffer+0x240 and the addresses are stored at errorbuffer+0x130+i*8 where i = 0->address count
The stack trace address count is stored at errorbuffer+0x240 and the addresses are stored at errorbuffer+0x130+i*8 where i = 0->address count
= fatal:p =
= fatal:p =
This is "nn::fatalsrv::IPrivateService".
{| class="wikitable" border="1"
|-
! Cmd || Name
|-
| 0 || GetFatalEvent
|}

Revision as of 22:04, 20 March 2018

fatal:u

This is "nn::fatalsrv::IService".

Cmd Name
0
1 FatalSimple
2 #TransitionToFatalError

TransitionToFatalError

Takes an input u64 errorcode and an unknown u64(TID maybe?). It also takes a type-0x15 error buffer and a pid-descriptor. The error buffer contains a stack trace. The stack trace address count is stored at errorbuffer+0x240 and the addresses are stored at errorbuffer+0x130+i*8 where i = 0->address count

fatal:p

This is "nn::fatalsrv::IPrivateService".

Cmd Name
0 GetFatalEvent