Project64 Debugger « 1 ... 3 4 5 6 7 »
Users browsing this thread: 1 Guest(s)

(29-03-2017, 09:38 AM)Nutta Wrote: The R4300i command window should pop up when it pauses

Thank you for the immediate reply! I really do appreciate it.

Hmmm...It'd appear that we might have half the problem here. The window wasn't appearing (but in many cases I did have it open as I'd been browsing it also). I assume that the breakpoint for a write is supposed to highlite where in the code the writing was done from...that's the bit that doesn't seem to have happened. My other thought is that I'm supposed to be reading the programme counter to figure out where the code block is.

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?

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.

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 Smile

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.
(This post was last modified: 31-03-2017, 01:18 AM by MRKane.)

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.

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
(This post was last modified: 09-04-2017, 06:40 AM by 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
(This post was last modified: 22-04-2017, 10:54 AM by shygoo.)


Attached Files
Size: 329 bytes / Downloads: 12 .cfg   Project64.cfg


04: Mario Cheer 
(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.  Chill  Thanks! (I just wish I could build latest git snapshots from your repo. Xbuild sadly fails, and I have no idea why.)
Quote:A word fitly spoken is like apples of gold in pictures of silver.
  --Proverbs 25:11

06: Mario Upset 
(Sorry, double post) It will not work for me.  Sad   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. Sad
(This post was last modified: 24-04-2017, 11:51 PM by J_128.)


Attached Files    
Quote:A word fitly spoken is like apples of gold in pictures of silver.
  --Proverbs 25:11

(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.  Sad   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. Sad

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?

(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.


Attached Files    
Quote:A word fitly spoken is like apples of gold in pictures of silver.
  --Proverbs 25:11

Project64 Debugger « 1 ... 3 4 5 6 7 »
Users browsing this thread: 1 Guest(s)