Closed mazen-mardini closed 4 years ago
Hi, I'll try to look into this, but I think this was changed between recent versions of PyCharm. Are you using stable or development build (edit: of the plugin)?
Actually reworking / adding support for debug variables / more idea variants is main change planned for next version of the plugin...
Thanks for a great plugin and a quick response!
I'm running the following version:
PyCharm 2019.3 (Community Edition)
Build #PC-193.5233.109, built on November 28, 2019
Runtime version: 11.0.4+10-b520.11 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
PyCharm is a stable build. I have it installed as a Snap-package on Ubuntu:
Name Version Rev Tracking Publisher Notes
pycharm-community 2019.3 169 stable jetbrains✓ classic
The plugin is the latest snapshot: 0.2.2 [2019-12-04]
I was not able to test this so far. In my test python script, I have z = bytearray(500)
which seems to be working for basic binary view. Not sure if my environment is different or there is some other means of declaring bytearray type in Python as I'm not familiar with this language enough I'm afraid.
Tested with PyCharm Community 2019.3.1 on Fedora 64 bit.
If possible please provide sample python script where view as binary fails.
I tried to provide some modified build with guessing attempt to workaround this, but I have strong doubts it will help.
You could use this script:
def f():
b = bytearray()
b += b'0000000'
print(b)
f()
Set the breakpoint on the print-call, run in debug-mode and then right-click the local variable b in the debugger and press View as Binary. That triggers the bug.
EDIT: I forgot one detail. I'm using PyPy 3.6.
I tried to fix this in version 0.2.2. Not sure if all forms of content are properly supported, thou.
Hello,
I'm getting the following exception when trying to open the hex-editor for a bytearray variable in Debug-mode (Python/PyCharm):