True, even in post-mortem debugging (assuming I have the objects from the heap), it's not like I'm going to exclude the addresses of objects in my write-ups (or as they're exposed via commands, such as !sosex.mdso[0]).
In native, if you're on the stack (e.g.: not using pointers), then addresses don't mean much of anything and if you're using pointers, memory optimisation means the address could mean feck-all after a cycle or two (assuming you've looking at an iDNA/TTT[1]).
So, to agree with you, who are agreeing with me: It is quite odd that this would be a principal argument for proquints.
In native, if you're on the stack (e.g.: not using pointers), then addresses don't mean much of anything and if you're using pointers, memory optimisation means the address could mean feck-all after a cycle or two (assuming you've looking at an iDNA/TTT[1]).
So, to agree with you, who are agreeing with me: It is quite odd that this would be a principal argument for proquints.
[0] - https://github.com/lowleveldesign/debug-recipes/blob/master/...
[1] - https://docs.microsoft.com/en-us/windows-hardware/drivers/de...