Editing PRX

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
= Overview =
scetool can decrypt SPRX's, producing an ELF... or is it? Not really. It has an ELF header but...


'''P'''laystation '''R'''elocatable E'''x'''ecutable (PRX)
First LOAD segment, paddr points to the descriptor for the "dependency table" or "deptable" for short:


= PRX2 =
NOTE: All addresses inside the file assume the ELF header isn't there (basically add 0xE0 to all addresses.)
{| class="wikitable"
! Offset
! Type
! Description
|-
| +0
| long
| Always(?) 0x101
|-
| +4
| char[28]
| Name of this PRX, padded out with zeroes. Doesn't necessarily match the file name(why?)
|-
| +32
| long
| A unique module ID? Gets used a lot later...
|-
| +36
| long
| Points to the deptable header
|-
| +40
| long
| Points to the END of the deptable header
|-
| +44
| long
| Points to the start of first deptable entry
|-
| +48
| long
| points to the end of the LAST deptable entry
|}


PRX2 is only present on PSVita. PSP and PS3 use PRX version 1.
Deptable header:
{| class="wikitable"
! Offset
! Type
! Description
|-
| +0
| long[5]
| Always(?) 0x1C000000, 0x80000002, 0x10000, 0, 0
|-
| +20
| long
| Points to three longs which are always(?) 0xBC9A0086, 0xAB779874, 0xD7F43016. The start of the mystery table.
|-
| +24
| long
| Points to three pointers in the mystery table. Two go to pointers to subroutines in the funcpointer table, the third goes back to the deptable descriptor.
|}


== Recognition ==
Entry in the deptable:
{| class="wikitable"
! Offset
! Type
! Description
|-
| +0
| short[2]
| Always(?) 0x2C00, 1
|-
| +4
| short
| Flags? 0x1 is always set, 0x8 often, 0x2000 seems to indicate a non-PRX library (like "stdc" or "allocator") that comes from somewhere else (LV2?)
|-
| +6
| short
| The number of functions the depending PRX needs from the depended PRX. There is this many function pointers in the stubtable (see below) for this PRX. Most of the time, there's also this many entries in the Mystery Table for that PRX. But not always? "allocator" in particular seems to get strange stuff.
|-
| +8
| short
| Usually 0, but "paf" gets sometimes 5, sometimes 6, sometimes 0. More flags maybe?
|-
| +10
| short[3]
| Always(?) 0. Probably for alignment.
|-
| +16
| long
| Pointer to the ASCII string of the depended PRX's name. These don't seem to consistently map with the PRX's file name in dev_flash.
|-
| +20
| long
| Pointer to this library's entries in the mystery table.
|-
| +24
| long
| Pointer to the the pointers to function wrappers for this library in the wrapper list.
|-
| +28
| long[2]
| 0, 0 for every PRX except paf, which gets two more sets in the mystery table, pointed to by these, unless +8 is 0.
|}


A PRX module is PRX2 format only if ehdr.e_type is ET_SCE_EXEC or ET_SCE_RELEXEC.
Second LOAD segment is all the relocation and symbol data, save for the names (as ASCII strings) of the exposed functions (which are in the first LOAD segment along with all the other strings the PRX uses).


A Program Segment is PRX2 format only if p_type is PT_SCE_RELA or PT_SCE_COMMENT.
At the start of this section is the wrapper list, just a flat array of pointers to subroutines that appear to be wrappers for calling functions in other PRXes. This combined with the deptable maps those wrappers to PRXes.


= Module Info =
At EOF-20 is a pointer to the start of the funcpointer table. After 0xFFFFFFFF and a handful of pointers into itself, it goes into a list of pointers to subroutines (as longs) each followed by a long containing the unique ID from the deptable descriptor.


PS3 and PSP PRX embed Module Info version 0.
Table number two: All longs(?) The very first is a pointer to the very start of the funcpointer table.


== Location ==
There is a table that's a listing of the functions exposed to apps/other PRXes. This table is usually referenced by a function; how exactly it is reached remains to be seen.
 
{| class="wikitable"
For PS3 (?and PSP?), it is located in text segment (first LOAD segment) at offset Elf32_Phdrs[text_seg_id].p_paddr - Elf32_Phdrs[text_seg_id].p_offset. Or more simply: at offset Elf32_Phdrs[text_seg_id].p_paddr in the ELF file.
! Offset
 
! Type
== Structure ==
! Description
 
|-
<source lang="C">
| +12n
#define MODULE_NAME_MAX_LEN 27
| long
 
| Pointer to the ASCII string name of this function
typedef struct sceModuleInfo_common { // size is 0x20
|-
  unsigned short modattr;
| +12n +4
  unsigned char modver[2];
| long
  char modname[MODULE_NAME_MAX_LEN];
| Pointer to this function's entry in the funcpointer table.
  unsigned char infover;
|-
} sceModuleInfo_common;
| +12n +8
 
| long
typedef struct sceModuleInfo_v0 { // size is 0x34
| Always(?) zero.
  sceModuleInfo_common c;
|}
  Elf32_Addr gp_value;
  Elf32_Addr libent_top;
  Elf32_Addr libent_btm;
  Elf32_Addr libstub_top;
  Elf32_Addr libstub_btm;
} sceModuleInfo_v0;
</source>
 
= Exports =
 
PS3 uses exports structure of size 0x1C ?or 0x28 in 64bits?.
 
<source lang="C">
typedef struct _scelibent_common { // size is 0x10
unsigned char size;
unsigned char auxattribute;
unsigned short version;
unsigned short attribute;
unsigned short nfunc;
unsigned short nvar;
unsigned short ntls;
unsigned char hashinfo;
unsigned char hashinfotls;
unsigned char reserved;
unsigned char nidaltsets;
} sceKernelLibraryEntryTable_common;
 
typedef struct _scelibent_1C { // size is 0x1C
sceKernelLibraryEntryTable_common c;
Elf32_Addr libname;
Elf32_Addr nid_table;
Elf32_Addr entry_table;
} sceKernelLibraryEntryTable_1C;
</source>
 
= Imports =
 
PS3 use imports structures of size 0x2C.
 
<source lang="C">
typedef struct _scelibstub_common { // size is 0xC
unsigned short size;
unsigned short version;
unsigned short attribute;
unsigned short nfunc;
unsigned short nvar;
unsigned short ntls;
} sceKernelLibraryStubTable_common;
 
typedef struct _scelibstub_2C { // size is 0x2C
sceKernelLibraryStubTable_common c;
unsigned char reserved[4];
Elf32_Addr libname;
Elf32_Addr func_nid_table;
Elf32_Addr func_entry_table;
Elf32_Addr var_nid_table;
Elf32_Addr var_entry_table;
Elf32_Addr tls_nid_table;
Elf32_Addr tls_entry_table;
} sceKernelLibraryStubTable_2C;
</source>
 
= Relocations =
 
== PS3 ==
 
Relocations can be found in either PT_SCE_PPURELA segments or SHT_SCE_PPURELA / SHT_RELA sections. RELA relocations are standard relocations while PPURELA relocations have 2 segment (program header) indexes stored in r_sym of r_info.
*The first index can be extracted with 0x7FFFFF00 as a mask and is used as a base address for r_addend. This sum will be the value applied to the patch.
*The second index can be extracted with 0x000000FF as a mask and is used as a base address for the target segment to patch and is added to r_offset.
*The first bit (0x80000000) is also set on earlier PRXs but it is currently unknown what it is used for.
 
 
 
{{File Formats}}
<noinclude>[[Category:Main]]</noinclude>
Please note that all contributions to PS3 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS3 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)