Psp2kerndmp: Difference between revisions

From Vita Development Wiki
Jump to navigation Jump to search
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 8: Line 8:
! name !! size in byte
! name !! size in byte
|-
|-
| Header || 0x34
| Header || 0xC
|-
| File info || 0x28 (+ variable?)
|-
|-
| fault info || variable
| fault info || variable
|}
|}
= Parse for dumped file =
[https://github.com/Princess-of-Sleeping/psp2kerndmp-parser psp2kerndmp-parser]


= Dump procedure =
= Dump procedure =
Line 27: Line 33:




Note: In versions 3.500.011 and later, when the flag set by [[SceSysmem#set_info_dump_flag|set_info_dump_flag]]is 1, ttyinfo is sent to the pc host instead of fault information, but due to a bug in the SCE code, most of the data sent is 0. increase
Note: In versions 3.500.011 and later, when the flag set by [[SceSysmem#set_info_dump_flag|set_info_dump_flag]] is 1, ttyinfo is sent to the pc host instead of fault information, but due to a bug in the SCE code, most of the data sent is 0. increase


If you have a kerneldebug qaf this is not a problem as some deci4p modules later call set_info_dump_flag(0).
If you have a kerneldebug qaf this is not a problem as some deci4p modules later call set_info_dump_flag(0).


set_info_dump_flag(0) is also called when SceKernelBlueScreenOfDeath starts normally.
set_info_dump_flag(0) is also called when SceKernelBlueScreenOfDeath starts normally.
[[Category:Formats]]

Latest revision as of 22:13, 1 May 2023

The .psp2kerndmp is a file containing failure information sent from the Development Kit to the pc host when the kernel fails

Format

name size in byte
Header 0xC
File info 0x28 (+ variable?)
fault info variable

Parse for dumped file

psp2kerndmp-parser

Dump procedure

First, SceExcpmgr catches DABT or kernel panic fault in the kernel and executes individual handlers.

And finally DABT handler of lowest excpmgr with priority 7 calls panic_on_kernel_exception.

panic_on_kernel_exception collects some fault information and writes them to shared memory.

Also, if the unit is a development kit, it passes the failure information to the deci4p module via sysroot.

And the deci4p module encrypts the failure information only in the absence of specific qa flags before sending it to the pc host.


Note: In versions 3.500.011 and later, when the flag set by set_info_dump_flag is 1, ttyinfo is sent to the pc host instead of fault information, but due to a bug in the SCE code, most of the data sent is 0. increase

If you have a kerneldebug qaf this is not a problem as some deci4p modules later call set_info_dump_flag(0).

set_info_dump_flag(0) is also called when SceKernelBlueScreenOfDeath starts normally.