Project64 Debugger

[shygoo]

Perhaps it's pausing on a DMA copy? The code at the program counter would look something like this:

Code:

​
LUI T0, 0xA460
SW T1, 0x000C (T0)

​

https://en.wikibooks.org/wiki/N64_Programming/Memory_mapping

MRKane Wrote:​
I've stripped and reinstalled PJ64 1.7 and 1.6 (for shits and giggles) but haven't had all that much luck with either. Is there a specific build that works best?

​

The plugin environment that installs with Pj64 2.3 works okay for me. I haven't experimented with anything else.

[MRKane]

I did to a check through the registers as the R4300i remains at the start of the memory block 80000000. I'll grab PJ64 2.3 and give it another crack with that version as dollars to doughnuts it's probably something really simple that I'm doing wrong!
EDIT: Nope, didn't help. It's just not taking me to where the current read, or program counter is. Everything else is working fine - I'll have a quick word on the chat thread and see if anyone can help there

Failing that: is there somewhere where the program counter is displayed so I could read that value to get the correct location instead? I should note (coming into a new forum and asking questions) that I do have a fair idea of what I'm doing but mainly specialised in Nemu hacking and good old fashioned GameShark hacking before my PC blew up (literally). I hark from the ShootersForever forums and have a bit of experience hardware side also.

[shygoo]

For posterity: In the O64 chat, we figured out this issue was occurring because the debugger wasn't taking TLB-mapping into account. This will be corrected in future releases.

[shygoo]

New stable snapshot is up -- For convenience, plugins and pre-configuration have been included this time.

Changes since last snapshot:

Add DMA logging window

​

Symbols:
  Add value auto-refreshing
  Implement saving
  Implement sort-by-address

Debugger:
  Fix broken floating point register fields
  Add COP0 register tab
  Add back & forward history buttons
  Add PC register field with goto button
  Add TLB-mapped address support
  Add code-editing features
  Make register fields monospace
  Move stack frame to its own window

​

Memory Viewer:
  Fix crash from invalid KSEG0 addresses
  Fix crash on window close
  Fix PAddr breakpoint issue
  Integrate DMA information
  Integrate symbol information

​

Memory Dumper:
  Reimplement assembly dumper

Memory Search:
  Improve scanning speed
  Open memory viewer on result double-click

Script Console:
  Add option to force-stop running scripts
  Make window resizeable
  Keep console window scrolled down
  Improve UI behavior when starting a script

Script API:
  Add debug.breakhere() function
  Add mem.getstring(addr) function
  Add numeric property access to gpr interface
  Add gpr.pc
  Add rom interface
  Add fpr interface

Settings:
  Add "Always use interpreter CPU" to advanced options

[shygoo]

If there are any Linux users that would like to run this with Wine, I found that the PJ64 Glide64 graphics plugin seems to work well. If the settings window doesn't work to change the graphics plugin, you can drop the attached file in the config folder.

Also while I'm in here, I added some nice cosmetic touches to the commands window

[J_128]

(22-04-2017, 10:33 AM)shygoo Wrote: If there are any Linux users that would like to run this with Wine, I found that the PJ64 Glide64 graphics plugin seems to work well. If the settings window doesn't work to change the graphics plugin, you can drop the attached file in the config folder.

Also while I'm in here, I added some nice cosmetic touches to the commands window
{-snip-}

​

That would be me.    Thanks! (I just wish I could build latest git snapshots from your repo. Xbuild sadly fails, and I have no idea why.)

[J_128]

(Sorry, double post) It will not work for me.     Whenever I try to open a ROM, I get this: (See Attachment)

Does anyone know what I can do?

​Edit: Yes, that is Linux. I would use it on windows but it doesn't start.

[queueRAM]

(22-04-2017, 11:56 AM)J_128 Wrote: I just wish I could build latest git snapshots from your repo. Xbuild sadly fails, and I have no idea why.

​

Isn't xbuild part of mono? This isn't a .Net project. It's C++ with ATL and some other fancy Windows things that I don't know much about. Not sure if it can be built easily under Linux, if at all.

(24-04-2017, 11:46 PM)J_128 Wrote: ​
It will not work for me.     Whenever I try to open a ROM, I get this: (See Attachment)

Does anyone know what I can do?

​Edit: Yes, that is Linux. I would use it on windows but it doesn't start.

​

This error message usually means you don't have plugins selected. Either you don't have plugins in the Plugins directory, or the ones specified in the config file aren't present. Under Windows, you'd be able to select them in the Settings. Not sure what can be done under Linux.

What do you mean it doesn't start under Windows?

[J_128]

(25-04-2017, 03:06 AM)queueRAM Wrote: Isn't xbuild part of mono? This isn't a .Net project. It's C++ with ATL and some other fancy Windows things that I don't know much about. Not sure if it can be built easily under Linux, if at all.

​

I know that this isn't a .Net project. I did some Google-ing on how to build a .sln file on Linux, and everything I read said that you use xbuild to build .sln file on Linux, so I tried it.

(25-04-2017, 03:06 AM)queueRAM Wrote: ​
What do you mean it doesn't start under Windows?

​

I mean that when I try to start it on Windows I get this: (See Attachment)

*sigh* I wish people would add support for those of us who still use Windows XP.

[shygoo]

For that Windows XP issue, try this build: http://shygoo.net/pj64d/Project64d%204-24-17.exe. I happened to replace that GetQueuedCompletionStatusEx function with an older one yesterday, since it was causing issues with Wine too.