Closed k4lizen closed 3 weeks ago
That's the error I see when I try to use vis
on an unmapped address.
The address in your example is 5 bytes long, which is uncommon in the x86_64 arch it says you're running on.
Could you check that this error occurs when using the command on mapped memory?
I don't remember the exact environment in which the crash happend because I figured that the stack trace is probably enough to figure out what caused the crash so
Could you check that this error occurs when using the command on mapped memory?
Is a bit tough, but the command generally does work for me with no problems when visualising actual heap chunks so
That's the error I see when I try to use vis on an unmapped address.
This is probably the issue. Is it really supposed to error out with an unreadable error if I give it an unmapped address though?
Error messages that make it clear if you made a mistake are definitely preferable to whatever gibberish Python emits in this scenario, so if you're keen on putting together a PR I reckon addressing it at the memory-read level could be a good start.
e.g. any command that expects a mapped virtual memory address could print something useful when passed an unmapped address. (though this can get difficult when only part of a struct is unmapped for example)
Keen to see what you come up with 👌
Heres the trace:
Gdb session history: