You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the dq and telescope interfaces are slightly different.
dq treats argument as a hex value, but telescope tries to parse it in some way. I think the behavior should be the same to make the UX better.
Steps to reproduce
see screenshots :)
My setup
pwndbg> show version
GNU gdb (Ubuntu 14.0.50.20230907-0ubuntu1) 14.0.50.20230907-git
pwndbg> py import sys; print(sys.version)
3.11.6 (main, Oct 8 2023, 05:06:43) [GCC 13.2.0]
pwndbg dev branch:
40b7928 (HEAD -> dev, origin/dev, origin/HEAD) fix missing cryptography 41.0.6 dependency in "nix" + add "release" workflow on pull_requests (#1955)
The text was updated successfully, but these errors were encountered:
This is not a bug, but a "feature" that we wanted to have the same interface as Windbg had with db/dw/dd/dq/ds commands.
But that's not the first time someone mentions this as an issue. We could maybe make this configurable if we want to give users the options how to deal with that, heh...
For me personally, it would make sense for commands to take hex values without the need for the "0x" prefix. Typically, hexadecimal values are used when working with the debugger. Feel free to close this "issue" or to push it forward :)
@rivit98 don't forget we generally accept gdb values within commands, so you can pass sth like some_var_name and its value will be automagically resolved. This is not the case for dX/eX (dq etc) commands iirc though.
Description
It seems that the
dq
andtelescope
interfaces are slightly different.dq treats argument as a hex value, but telescope tries to parse it in some way. I think the behavior should be the same to make the UX better.
Steps to reproduce
see screenshots :)
My setup
The text was updated successfully, but these errors were encountered: