2 ms·
Yes, that debugger example really confused me and made me wonder why he added it. Anyone who has actually done live-debugging sessions will know that hex is per
by userbinator 8y ago
Yes, that debugger example really confused me and made me wonder why he added it. Anyone who has actually done live-debugging sessions will know that hex is perfectly pronouncible, and furthermore is a direct mapping to binary.
- renholder 8y agoTrue, 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. [0] - https://github.com/lowleveldesign/debug-recipes/blob/master/debugging-using-windbg/sosex.help.txt https://github.com/lowleveldesign/debug-recipes/blob/master/... [1] - https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/time-travel-debugging-record https://docs.microsoft.com/en-us/windows-hardware/drivers/de...