-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reverse engineering: Call Graph and Flow Chart failing to render #108
Comments
I found the problem. In 3.2 I changed to esbuild packaging. But that dropped the flowchart etc. functionality. |
I installed that revised extension but when I launch DeZog it briefly shows the disassembly control bar, but with the 'continue' button missing, and after a few seconds the control bar disappears and no active debug session occurs. I noticed with version 3.2.1 it shows 'DeZogPlugin v2.1.0.31481' initialized, in the console, but nothing appears in the revised version. I then checked the VS Code extension log and it shows this...
I can confirm that in the unpacked extension location in .vscode the referenced package "@aduh95/viz.js" is missing from the node_modules directory. |
This all has something to do with the esbuild bundler. |
Excellent those features are working now! The flow chart and caller graphs are both appearing and look to be really powerful and useful to get an overview of the code structure. Not used the smart disassembly yet but I see that you have updated the documentation on reverse engineering so will take a close read through that now that everything is working. Also not experiencing any 'blocking' when running any of these features. |
Good to hear that it is working. |
I am using the reverse engineering feature and am able to build up a personal disassembly file from a .nex binary running on CSpect. However when I try to generate a "Call Graph" or "Flow Chart" I get an initial error in the console
subsequent attempts give the error
It is the same regardless of the binary I use or the location in the disassembly file (either personal or "disasm.list"). I tried with your sample Next program "z80-sample-program.nex" and the same "fill_bckg_line" subroutine shown in the example (at address $6017) and I get the same errors.
I am on Windows 10 Home (22H2) and running...
VS Code v1.75.1
DeZog v3.2.1
CSpect v2.19.1.0 (with DeZogPlugin v2.1.0.31481)
The text was updated successfully, but these errors were encountered: