[BUG]: Debugger - Memory Search - Changed/Unchanged Search Filter Filters Out Addresses Improperly (When searching for a 4 Byte, Float, or Double value)

[Joshua-1248]

Describe the Bug

Changed/Unchanged Search Filter Filters Out Addresses Improperly (When searching for a 4 Byte, Float, or Double value)

Reproduction Steps

Start a Not Equal To (shown as 'Not Equals' in the Debugger) search with the Byte Type set to 4 Bytes (or Float/Double), and the starting value of 0 (workaround to do Unknown Value Searching as it is not implemented yet), then attempt multiple Changed/Unchanged filter searches while looking for something like the player's position.

Afterwards, the debugger will return a couple of addresses but it seems to fail to return addresses properly. Likely incorrectly filtering out what may as well have been the correct addresses.

Doing the same steps above, but instead doing a 2 byte search, appears to work a little better with the Changed\Unchanged searching.

Maybe it is something to do with the rate of how the Debugger is trying to return values, but is late in fetching addresses, causing some addresses to be filtered out incorrectly, or something else.

Expected Behavior

Debugger should properly return addresses when doing an Unchanged/Changed memory search without misfiltering results.

PCSX2 Revision

PCSX2 v2.3.40

Operating System

Linux (64bit) - Specify distro below

If Linux - Specify Distro

Linux Mint 22 Cinnamon - Wilma

Logs & Dumps

No response

[Berylskid]

Can you share any ACTUAL example of wrong result and expected result?

[Joshua-1248]

When attempting to find the player's XYZ position addresses:

2024-12-19.22-40-06.mp4

[Berylskid]

Can you add some context? Like what is displayed wrongly / what is supposed to be shown

[Joshua-1248]

The debugger's functionality for changed/unchanged search types doesn't work properly, simply put.