louve
Forum Noob
Hello friends,
I have a PS2 with OPL and no matter which version I use, there is a specific game (SLUS_211.43) that has a specific freeze (when selecting a multiplayer character and confirming) that is not reported anywhere as far as I can see. People report the game either freezing on the title screen, or working fine on SMB "can play the game and save and load singleplayer" (which is true on my version too) but nobody seems to be reporting the multiplayer does not work, probably because it's not played much.
Since I do programming on a daily basis and a bit of debugging/reverse engineering too, and since this bug has a 100% repro rate, I was curious to look into it myself before making a more extensive report.
Therefore I would like to know how to get started debugging & testing OPL once it's built from source
- Should I run OPL with PCSX2, does it have a debugger or should I attach a traditional debugger like windbg to PCSX?
- Should I run OPL under some other setup that allows debugging from Windows / Linux directly?
- Or does OPL require a PS2 Dev kit for any debugging, and can only be debugged on real hardware?
- Or can it not be debugged at all and I have to "trial and error" every possible combination of flags and changes on real hardware every time, to see and understand what could cause the freeze to occur?
Is there a way to make the PS2 produce a crash dump when it has hanged?
Otherwise, can a crashdump produced from PCSX2 OPL be of any use or will it be "too far" from the real hardware/real conditions?
If I could get started with the project in a few simple steps to reproduce my freeze in a more controlled setup where I can observe the registers & code hanging, that would be really sweet, and maybe I could save some time to the developers investigating it next. I'd love to go as far as submitting a patch myself to fix it, if that is ever possible.
Thanks
I have a PS2 with OPL and no matter which version I use, there is a specific game (SLUS_211.43) that has a specific freeze (when selecting a multiplayer character and confirming) that is not reported anywhere as far as I can see. People report the game either freezing on the title screen, or working fine on SMB "can play the game and save and load singleplayer" (which is true on my version too) but nobody seems to be reporting the multiplayer does not work, probably because it's not played much.
Since I do programming on a daily basis and a bit of debugging/reverse engineering too, and since this bug has a 100% repro rate, I was curious to look into it myself before making a more extensive report.
Therefore I would like to know how to get started debugging & testing OPL once it's built from source
- Should I run OPL with PCSX2, does it have a debugger or should I attach a traditional debugger like windbg to PCSX?
- Should I run OPL under some other setup that allows debugging from Windows / Linux directly?
- Or does OPL require a PS2 Dev kit for any debugging, and can only be debugged on real hardware?
- Or can it not be debugged at all and I have to "trial and error" every possible combination of flags and changes on real hardware every time, to see and understand what could cause the freeze to occur?
Is there a way to make the PS2 produce a crash dump when it has hanged?
Otherwise, can a crashdump produced from PCSX2 OPL be of any use or will it be "too far" from the real hardware/real conditions?
If I could get started with the project in a few simple steps to reproduce my freeze in a more controlled setup where I can observe the registers & code hanging, that would be really sweet, and maybe I could save some time to the developers investigating it next. I'd love to go as far as submitting a patch myself to fix it, if that is ever possible.
Thanks
