This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Ghost in the Shell - Stand Alone Complex -Europe -ULES00135
#1
r3595

After logo,raise
ERROR memory - read16 - Invalid memory address: 0x0000000D PC=0x09E78D5C

full debug log not work
edit :add PPSSPP log (work)


Attached Files
.txt   infolog.txt (Size: 15.29 KB / Downloads: 64)
.7z   compilerdebuglog.7z (Size: 488.67 KB / Downloads: 80)
.txt   ppssppinfolog.txt (Size: 30.67 KB / Downloads: 65)
.7z   ppssppdebuglog.7z (Size: 404.32 KB / Downloads: 86)
Reply
#2
Code:
19:46:58 DEBUG compiler - user_main - CodeInstruction.compile  > 0x9E78950 - addiu      $a0, $zr, 1 <=> li $a0, 1
19:46:58 DEBUG compiler - user_main - CodeInstruction.compile    0x9E78954 - addu       $a1, $zr, $zr <=> li $a1, 0
19:46:58 DEBUG compiler - user_main - CodeInstruction.compile <  0x9E78958 - jal        0x09E829C8 [sceKernelSelfStopUnloadModule]
19:46:58 DEBUG compiler - user_main - CodeInstruction.compile    0x9E7895C - addu       $a2, $zr, $zr <=> li $a2, 0
Great information! I have fixed this function in r3597. Could you retest?

Thank you!
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#3
compile error by r3596
I think that same reason that Automated Jpcsp builds broke
   
Reply
#4
(08-28-2014, 07:22 PM)sum2012 Wrote: compile error by r3596
I think that same reason that Automated Jpcsp builds broke
Thank you for the hint! I had no issue using eclipse. Should be fixed in r3598...
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#5
r3598
Can move to Intro Section
The game raise
Invalid memory address: 0x77777783 PC=0x08852990
after below picture press start.Magicly,USA version work.(Same case as PPSSPP)
   
Attach both Europe and USA version 's info and compiler log.


Attached Files
.txt   EUR-info-log.txt (Size: 34.24 KB / Downloads: 62)
.7z   EUR-compiler-log.7z (Size: 1.52 MB / Downloads: 89)
.txt   USA-info-log.txt (Size: 37.22 KB / Downloads: 65)
.7z   USA-compiler-log.7z (Size: 1.6 MB / Downloads: 87)
Reply
#6
Could you try to generate an INFO log for both versions (EUR and US) with the following lines added in your LogSettings.xml:
Code:
<logger name='hle.SysMemUserForUser'> <level value='trace' /> </logger>
<logger name='hle.ThreadManForUser'> <level value='debug' /> </logger>
<logger name='hle.ModuleMgrForUser'> <level value='debug' /> </logger>
Thank you!
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#7
r3731 no change
It does not display menu in 30 minute for 'hle.ThreadManForUser' debug log.
Attach is without 'hle.ThreadManForUser' debug log
(03-11-2015, 03:44 PM)gid15 Wrote: Could you try to generate an INFO log for both versions (EUR and US) with the following lines added in your LogSettings.xml:
Code:
<logger name='hle.SysMemUserForUser'> <level value='trace' /> </logger>
<logger name='hle.ThreadManForUser'> <level value='debug' /> </logger>
<logger name='hle.ModuleMgrForUser'> <level value='debug' /> </logger>
Thank you!


Attached Files
.7z   eur_log_r3731.7z (Size: 42.77 KB / Downloads: 85)
.7z   usa_log_r3731.7z (Size: 44.21 KB / Downloads: 81)
Reply
#8
Code:
05:20:03 DEBUG hle.SysMemUserForUser - KokakuLoad - malloc partition=2, name='ThreadMan-Fpl-0xa8-libatrac3plus.prx', type=PSP_SMEM_Low, size=0x5000, addr=0x00000000: returns 0x0881C800
...
05:20:03 DEBUG hle.ModuleMgrForUser - KokakuLoad - sceKernelLoadModule path=0x09FB88E0('disc0:/PSP_GAME/USRDIR/modules.psp/libatrac3plus.prx'), flags=0x0, optionAddr=0x09FB88C0
...
05:20:03 DEBUG hle.SysMemUserForUser - KokakuLoad - malloc partition=2, name='ThreadMan-Fpl-0xd1-libfont.prx', type=PSP_SMEM_Low, size=0xA900, addr=0x00000000: returns 0x08821800
...
05:20:03 DEBUG hle.ModuleMgrForUser - KokakuLoad - sceKernelLoadModule path=0x09FB88E0('disc0:/PSP_GAME/USRDIR/modules.psp/libfont.prx'), flags=0x0, optionAddr=0x09FB88C0
Interesting, this game seems to have a very strict memory management where it is often allocating the whole PSP memory.

Before loading the libatrac3plus.prx, it is reserving an Fpl block with the same name and then free it. This block has a size of 0x5000, maybe an indication that the game expects the libatrac3plus.prx to use 0x5000 bytes of memory...

The same happens for libfont.prx with a size of 0xA900.
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#9
(03-13-2015, 08:29 AM)gid15 Wrote:
Code:
05:20:03 DEBUG hle.SysMemUserForUser - KokakuLoad - malloc partition=2, name='ThreadMan-Fpl-0xa8-libatrac3plus.prx', type=PSP_SMEM_Low, size=0x5000, addr=0x00000000: returns 0x0881C800
...
05:20:03 DEBUG hle.ModuleMgrForUser - KokakuLoad - sceKernelLoadModule path=0x09FB88E0('disc0:/PSP_GAME/USRDIR/modules.psp/libatrac3plus.prx'), flags=0x0, optionAddr=0x09FB88C0
...
05:20:03 DEBUG hle.SysMemUserForUser - KokakuLoad - malloc partition=2, name='ThreadMan-Fpl-0xd1-libfont.prx', type=PSP_SMEM_Low, size=0xA900, addr=0x00000000: returns 0x08821800
...
05:20:03 DEBUG hle.ModuleMgrForUser - KokakuLoad - sceKernelLoadModule path=0x09FB88E0('disc0:/PSP_GAME/USRDIR/modules.psp/libfont.prx'), flags=0x0, optionAddr=0x09FB88C0
Interesting, this game seems to have a very strict memory management where it is often allocating the whole PSP memory.

Before loading the libatrac3plus.prx, it is reserving an Fpl block with the same name and then free it. This block has a size of 0x5000, maybe an indication that the game expects the libatrac3plus.prx to use 0x5000 bytes of memory...

The same happens for libfont.prx with a size of 0xA900.
These findings have been added in r3736. Could you update the log file?

Thank you!
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#10
Updated the log to r3736
Anyway,I can do JPCSPTrace log...
(03-20-2015, 06:08 PM)gid15 Wrote:
(03-13-2015, 08:29 AM)gid15 Wrote:
Code:
05:20:03 DEBUG hle.SysMemUserForUser - KokakuLoad - malloc partition=2, name='ThreadMan-Fpl-0xa8-libatrac3plus.prx', type=PSP_SMEM_Low, size=0x5000, addr=0x00000000: returns 0x0881C800
...
05:20:03 DEBUG hle.ModuleMgrForUser - KokakuLoad - sceKernelLoadModule path=0x09FB88E0('disc0:/PSP_GAME/USRDIR/modules.psp/libatrac3plus.prx'), flags=0x0, optionAddr=0x09FB88C0
...
05:20:03 DEBUG hle.SysMemUserForUser - KokakuLoad - malloc partition=2, name='ThreadMan-Fpl-0xd1-libfont.prx', type=PSP_SMEM_Low, size=0xA900, addr=0x00000000: returns 0x08821800
...
05:20:03 DEBUG hle.ModuleMgrForUser - KokakuLoad - sceKernelLoadModule path=0x09FB88E0('disc0:/PSP_GAME/USRDIR/modules.psp/libfont.prx'), flags=0x0, optionAddr=0x09FB88C0
Interesting, this game seems to have a very strict memory management where it is often allocating the whole PSP memory.

Before loading the libatrac3plus.prx, it is reserving an Fpl block with the same name and then free it. This block has a size of 0x5000, maybe an indication that the game expects the libatrac3plus.prx to use 0x5000 bytes of memory...

The same happens for libfont.prx with a size of 0xA900.
These findings have been added in r3736. Could you update the log file?

Thank you!


Attached Files
.7z   EUR_log_r3736.7z (Size: 36.8 KB / Downloads: 82)
.7z   USA_log_r3736.7z (Size: 38.69 KB / Downloads: 82)
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)