follow five exported dispatchers in the local system module. retain opaque payload pointers and document unresolved layouts instead of guessing their fields. throwing stub bodies remain unchanged.
2.5 KiB
libSceNpSessionSignaling technical debt
Unknown function info
-
sceNpSessionSignalingGetConnectionStatistics (libSceNpSessionSignaling) - unknown signature
-
sceNpSessionSignalingGetConnectionStatus (libSceNpSessionSignaling) -
(int32 context id, int32 connection id, int32* status, SceNetInAddr* peer address, uint16* peer port)is ASTRO BOT's (PPSA21564 01.007.000) call at 0x30622B: the context id from a 32-bit field, the connection id, three stack outputs, a negative result taken as an error, then the address passed tosceNetInetNtop(AF_INET, ...)and the port tosceNetNtohs. It matches PS4'ssceNpSignalingGetConnectionStatus. The title reaches it only for a connection id from the signaling library, which offline never hands one out. No session ever activates offline, so every connection id answersCONN_NOT_FOUND(0x8055330C, from shadPS4) without writing the outputs, and a null status answersINVALID_ARGUMENT. The context id is not checked, as contexts are not tracked. The console's answer for an unknown context or connection is unverified -
sceNpSessionSignalingCreateJoinActivate, sceNpSessionSignalingGetConnectionFromNetAddress, sceNpSessionSignalingGetCustomProperty, sceNpSessionSignalingGetGroupFromPeerAddress, sceNpSessionSignalingInitializeWithPort, sceNpSessionSignalingJoinActivate and sceNpSessionSignalingSetCustomProperty (libSceNpSessionSignaling) - names and NIDs are present in the PS5 3.20 export inventory, but no credible prototypes were found. They are declared without parameters solely to resolve known imports; this is not an ABI claim.
-
sceNpSessionSignalingGetMemoryInfo, sceNpSessionSignalingGetConnectionFromPeerAddress, sceNpSessionSignalingGetGroupFromSessionId, sceNpSessionSignalingGetGroupInfo, sceNpSessionSignalingGetConnectionFromNetAddress2 - argument registers and scalar widths follow the system module exports
lbXTXRG5nyM,dJJ0UPrrsok,UGcXquhVYrY,WtOs6cUbrx8andhbNcE4fnBDs. Pointer payloads remain opaque: their layouts and the address-type values require tracing the virtual callees. All five exports remain throwing stubs.