question regarding breakpoints

[grief3r]

what exactly is a memory breakpoint and how does it work,

also let's say i wanted the emulator to pause whenever a value is written to memory that isn't an instruction, how would i do that?

[[Unknown]]

Well, currently they pause the emulator when any value is written to that address. It's possible to add condition support but a little bit of a pain so no one has done it yet.

You can do an address range. It doesn't support writes from HLE, though (video, memcpy, etc.)

What do you mean by, "isn't an instruction?" It breaks on MIPS instructions like "sw", "sv.q", etc. It doesn't know whether it's writing an instruction, texture data, stack, etc.

-[Unknown]

[grief3r]

(12-11-2013 05:35 AM)[Unknown] Wrote:  Well, currently they pause the emulator when any value is written to that address. It's possible to add condition support but a little bit of a pain so no one has done it yet.

You can do an address range. It doesn't support writes from HLE, though (video, memcpy, etc.)

What do you mean by, "isn't an instruction?" It breaks on MIPS instructions like "sw", "sv.q", etc. It doesn't know whether it's writing an instruction, texture data, stack, etc.

-[Unknown]

id like to try this condition support whats the syntax

[dlanor]

(12-11-2013 04:43 PM)grief3r Wrote:  id like to try this condition support whats the syntax

I think you misunderstood what '[Unknown]' said about 'condition support'.
What he said simply means that such support is not yet implemented.
So there is no way for anyone to try it with the current versions.

Best regards: dlanor

[grief3r]

well i just noticed this old thread and wondering if this yet support conditional breakpoints

"What do you mean by, "isn't an instruction?" It breaks on MIPS instructions like "sw", "sv.q", etc. It doesn't know whether it's writing an instruction, texture data, stack, etc."

i didnt quite understand how breakpoints worked at the time but i was referring to whenever an instruction to be executed gets replaced with another for instance when you switch to a different screen such as the main menu the address storing that instruction becomes a completely different one, which i have actually tried doing and it does break at the instruction writing over that piece of memory.

[[Unknown]]

Oh, sure. Ultimately, that is just a sw usually.

Although, another case for that might be "relocations". This is where the OS (which is HLE) automatically modifies pointers for you between loaded modules. I'm not sure offhand if those trigger breakpoints right now...

-[Unknown]