SceCoredump: Difference between revisions

From Vita Development Wiki
Jump to navigation Jump to search
Line 26: Line 26:
| 3.60 || [[SceCoredump#SceCoredumpForDriver|SceCoredumpForDriver]] || ? || Kernel || 0xA351714A
| 3.60 || [[SceCoredump#SceCoredumpForDriver|SceCoredumpForDriver]] || ? || Kernel || 0xA351714A
|-
|-
| 3.60 || [[SceCoredump#SceCoredumpForDriver|SceCoredump]] || ? || User || 0xA143A77F
| 3.60 || [[SceCoredump#SceCoredump|SceCoredump]] || ? || User || 0xA143A77F
|-
|-
| 3.60 || [[SceCoredump#SceCoredumpForDriver|SceCoredumpNounlink]] || ? || User || 0x2646E9D8
| 3.60 || [[SceCoredump#SceCoredumpNounlink|SceCoredumpNounlink]] || ? || User || 0x2646E9D8
|}
|}



Revision as of 23:40, 27 January 2018

Module

Known NIDs

Version Name World Privilege NID
1.69 SceCoredump Non-secure Kernel 0x4CB1F0CC
3.60 SceCoredump ? Kernel 0x3E0F5EBD

Libraries

Though it may be possible to enable some Coredump features via setting registry values, patching for creating full Coredumps on retails is required. There are 2 key patches.

In the SceCoredump module, there are two functions that read values from the registry. The registry key used is "/CONFIG/COREDUMP". The first patch is to force the function that checks the key "enable_coredump" to return 1. The second is to force the function that checks the key "dump_level" to return 0xEF0. They are at base+0x3070 and base+0x3000 respectively on 1.50.

Known NIDs

Version Name World Visibility NID
1.69 SceCoredumpForDriver Non-secure Kernel 0xA351714A
3.60 SceCoredumpForDriver ? Kernel 0xA351714A
3.60 SceCoredump ? User 0xA143A77F
3.60 SceCoredumpNounlink ? User 0x2646E9D8

SceCoredumpForDriver