Changes

| style="background: red" | No

| style="background: red" | No

| style="background: red" | No

| style="background: red" | No

| Result [[IPC|ReplyAndReceive]](s32* index, Handle* handles, s32 handleCount, Handle replyTarget)

| Result [[IPC#svcReplyAndReceive|ReplyAndReceive]](s32* index, Handle* handles, s32 handleCount, Handle replyTarget)

|

|

|-

|-

|-

|-

| u32

| u32

| Flags. Bit0 means that svcContinueDebugEvent needs to be called for this event (except for EXIT PROCESS events, for which you need to call svcContinueDebugEvent even if this bit is clear)

| Flags. Bit0 means that svcContinueDebugEvent needs to be called for this event

|-

|-

| u8[4]

| u8[4]

| 2

| 2

|-

|-

| EXIT PROCESS

| EXIT PROCESS (1)

| 3

| 3

|-

|-

| 4

| 4

|-

|-

| DLL LOAD *

| DLL LOAD (3)

| 5

| 5

|-

|-

| DLL UNLOAD *

| DLL UNLOAD (3)

| 6

| 6

|-

|-

| SCHEDULE IN **

| SCHEDULE IN (1) (2)

| 7

| 7

|-

|-

| SCHEDULE OUT *

| SCHEDULE OUT (1) (2)

| 8

| 8

|-

|-

| SYSCALL IN *

| SYSCALL IN (1) (2)

| 9

| 9

|-

|-

| SYSCALL OUT *

| SYSCALL OUT (1) (2)

| 10

| 10

|-

|-

| 11

| 11

|-

|-

| MAP *

| MAP (1) (2)

| 12

| 12

|}

|}

<nowiki>*</nowiki> Unused

<nowiki>(1)</nowiki> Non-blocking: all other events preempt and block all the threads of their process until they are continued.

 

<nowiki>**</nowiki> Referenced but never used in practise

<nowiki>(3)</nowiki> Completely removed from the kernel, but referenced in DMNT. Stubbed relocation code (e.g., in Process9 and in PXI sysmodule) and even whole libraries (e.g., in PXI sysmodule's .rodata section) seem to indicate that Nintendo used dynamic libraries early in system development.

When calling svcDebugActiveProcess, an ATTACH PROCESS debug event is signaled, then ATTACH THREAD for each of its opened threads, then finally ATTACH BREAK.

When calling svcDebugActiveProcess, an ATTACH PROCESS debug event is signaled, then ATTACH THREAD for each of its opened threads, then finally ATTACH BREAK.

| 1

| 1

|-

|-

| UNHANDLED EXCEPTION

| DEBUG TERMINATE

| 2

| 2

|}

|}

| No

| No

| Arguments: <code>u32 what, u64 val</code>

| Arguments: <code>u32 what, u64 val</code>

UNITINFO needs to be non-zero.  

UNITINFO needs to be non-zero for <code>what</code> 1 and 2.  

If <code>what</code> is 0 or any invalid value, nothing is done.  

If <code>what</code> is 0 or any invalid value, nothing is done.  

If it is 1, <code>val != 0</code> is written to the global variable enabling ERR:F-format register dumps on user-mode CPU/VFP exceptions (the VFP exception handler acts as if this variable was always true and works on retail environments). The user handler, stack pointer to use for exception handling, and pointer to use for the exception info structure are contiguously located in either the thread's TLS, or if the handler is NULL, in the main thread's TLS, at offset 0x40. If the specified stack pointer is 1, sp_usr - 0x5c is used instead; if the specified exception info buffer is 1, sp_usr - 0x5c is used instead, and if it is 0, <specified stack> - 0x5c is used (0x5c is the size of the exception info structure that is being pushed). Configured by NS on startup on dev-units (default being 0 on non-debugger/jtag units).

If it is 1, <code>val != 0</code> is written to the global variable enabling ERR:F-format register dumps on user-mode CPU/VFP exceptions (the VFP exception handler acts as if this variable was always true and works on retail environments). The user handler, stack pointer to use for exception handling, and pointer to use for the exception info structure are contiguously located in either the thread's TLS, or if the handler is NULL, in the main thread's TLS, at offset 0x40. If the specified stack pointer is 1, sp_usr - 0x5c is used instead; if the specified exception info buffer is 1, sp_usr - 0x5c is used instead, and if it is 0, <specified stack> - 0x5c is used (0x5c is the size of the exception info structure that is being pushed). Configured by NS on startup on dev-units (default being 0 on non-debugger/jtag units) using the 0x000F0000 configuration block in the [[Config_Savegame|config savegame]].

If 2, kernelpanic will be called when svcBreak is used by a non-attached process. Configured by NS on startup on dev-units (default being 0 on non-debugger/jtag units).

If 2, kernelpanic will be called when svcBreak is used by a non-attached process. Configured by NS on startup on dev-units (default being 0 on non-debugger/jtag units) using the 0x000F0000 configuration block in the [[Config_Savegame|config savegame]].

If 3, this changes the scheduling/preemption mode (when no threads are being preempted, otherwise returns error 0xC8A01414), see [[KResourceLimit]] for more details.

If 3, this changes the scheduling/preemption mode (when no threads are being preempted, otherwise returns error 0xC8A01414), see [[KResourceLimit]] for more details.

| 7

| 7

|  

|  

| Returns 0

| Returns the number of threads of the process

|-

|-

| 8

| 8

|-

|-

| 1

| 1

| Get internal refcount for kernel object (not counting the one this SVC adds internally to operate), and also a boolean if it is 0 (prior to substracting 1, as explained before).

| Get internal refcount for kernel object (not counting the one this SVC adds internally to operate), sign-extended to 64 bits.

| Unimplemented, returns an uninitialized u64 variable (corresponding to r5-r6, which were not altered outside of userland).

|-

|-

| 0x32107

| 0x32107