search

fudgepop01 / kaitai_ide_vscode

A VSCode extension built to assist the creation and debugging of kaitai struct files
GNU General Public License v3.0
22 stars 1 forks source link

KSExplorer is empty #15

Open jackhab opened 3 years ago

jackhab commented 3 years ago

I just installed Kaitai 0.7.0 and followed Usage instructions to open a small jpeg file with ksy file from format gallery and KSExplorer remains empty without any errors/warning (while jpeg is loaded in the hex editor). Any ways to debug/analyze this issue?

nokaitai

Puyodead1 commented 2 years ago

same issue for me, clicking "compile and examine" or "compile to target language" do nothing

Edit: Looks like its just extremely slow, It finally loaded after about 10 minutes

toog commented 2 years ago

Same for me "compile and examine KSY" do nothing but "Compile To Targuet Language" work well.

image

Tested with vscode in Linux Ubuntu and Windows Version : 1.71.2 Electron : 19.0.12 Chromium : 102.0.5005.167 Node.js : 16.14.2 V8 : 10.2.154.15-electron.0 Système d’exploitation : Linux x64 5.15.0-50-generic snap Sandboxé : No

ianfhunter commented 10 months ago

Same issue here. It appears to be an issue linked with the name of the file:

my ksy file here is wts.ksy and the error changes if i change the name

 2024-01-08 16:51:22.382 [error] ReferenceError: Wts is not defined
    at eval (eval at compileFunction (c:\Users\ianhunter\.vscode\extensions\fudgepops.kaitai-struct-vscode-0.9.0\dist\extension.js:108944:12), <anonymous>:28:1)
    at _HexEditor.updateKaitaiStruct (c:\Users\ianhunter\.vscode\extensions\fudgepops.kaitai-struct-vscode-0.9.0\dist\extension.js:108711:22)
    at CompileAndExamineCommand.execute (c:\Users\ianhunter\.vscode\extensions\fudgepops.kaitai-struct-vscode-0.9.0\dist\extension.js:108107:41)
    at async r.h (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:107:82736)
guill commented 1 week ago

@ianfhunter's discovery that the error changes depending on the file's name was the clue I needed to figure out a workaround. Make sure the id in your meta section matches the name of the file. For example, if your file starts with:

meta:
  id: my_protocol
  endian: be

then your file must be named my_protocol.ksy for this extension to work.