stef-levesque/vscode-hexdump

hexdump file not updated when binary changes

Closed this issue · 9 comments

watersne commented

Extension Version 1.7.2, VS Code Version: 1.38.1. OS: Linux

The hexdump seems to rely on some cached version of the binary, or cache the .hexdump file somewhere. As I make changes to the binary they aren't reflected in the hexdump.

Steps:

  1. Generate a binary
  2. Show the hexdump of the binary
  3. Close the hexdump of the binary
  4. Change the source and regenerate the binary
  5. Show the hexdump. The hexdump remains unchanged from before, but the binary has changed.
joeywang4 commented

I think I have solved this issue.
You can try it out at #67.

Deleted user commented

Will this fix be applied to the current VS Code extension soon? I have to use command line hexdump like a sucker at the moment.

leohoe commented

I'm running into the same issue.
The current VS Code extension still does not update the hexdump when the file changes.

filipux commented

I'm seeing this problem on macOS too

iliazeus commented

@watersne, I resolved this issue in my fork: https://github.com/iliazeus/vscode-hexdump.

The fix was to simply invalidate the cache when a corresponding hexdump is closed.

Marketplace link

stef-levesque commented

Fixed in version 1.8.0

Niko-O commented

I have version 1.8.1 installed and this still happens.
VS Code version is 1.51.1

Jed-Z commented

I encountered the same problem in 'Remote - WSL'. Hexdump results won't change when the binary changes, unless I reload the window.

hexdump for VSCode v1.8.1
VS Code Version 1.55.2 on Windows

jiisamitt commented

i recommend using another viewer like hex editor, that worked for me