Difference between revisions of "SceCoredump"
Jump to navigation
Jump to search
Devnoname120 (talk | contribs) (Swapped Module <-> Library, see revision 1.1 under "Revision History" of "Vita SDK specifications" (https://wiki.henkaku.xyz/vita/File:Vita_SDK_specifications.pdf)) |
|||
| Line 1: | Line 1: | ||
| − | == | + | == Module == |
=== Known NIDs === | === Known NIDs === | ||
| Line 9: | Line 9: | ||
|} | |} | ||
| − | == | + | == 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. | 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. | ||
| Line 25: | Line 25: | ||
== SceCoredumpForDriver == | == SceCoredumpForDriver == | ||
| − | [[Category: | + | [[Category:Modules]] |
[[Category:Kernel]] | [[Category:Kernel]] | ||
Revision as of 03:41, 9 November 2016
Module
Known NIDs
| Version | Name | World | Privilege | NID |
|---|---|---|---|---|
| 1.69 | SceCoredump | Non-secure | Kernel | 0x4CB1F0CC |
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 |