Opening monitor in vice after build+run makes vice hang

[npup]

Hi!

..and thank you for this project. I especially enjoy the editor support for jumping between labels etc which is lacking in some other extensions in this field.

I have come across a problem, however.

Problem: When I try to start the monitor via the menu (or by pressing Cmd-Esc), the spinning beach ball (of death, it will soon be apparent) shows up. x64sc turns "unresponsive" and must be force-killed. The problem can be avoided by quitting vscode after vice have started, but before trying to open the monitor (this is not very practical, however). It seems that vscode has some kind of tie to the vice process that prevents this action from working properly.

My setup runs vscode and has an installation of java+kickassembler v5.25 and vice v3.9 (GTK) (tried other versions of vice too). The extension is configured with path to kickassembler's directory and to the vice binary (.../path/to/bin/x64sc), and building+running projects work great 👍.(this is on Mac, though I have an equivalent setup on Windows that behaves the same).

I lack the expertise to understand what is happening, and have described it best as i can. The same thing happens for me under windows. Happy to try and describe it better if you cannot replicate it easily and/or have some further questions.

Kind regards /p

Edit: To be clear, the monitor opens fine when using it from "not within vscode" and having it started in this way, by the extension.

[rolandshacks]

Hi.

I think the symptoms you're describing reflect how Vice actually handles monitor interaction. All is exclusive synchronous access, and while vs64 has an open connection to send remote monitor commands, the built-in monitor interface (as part of the Vice user interface) is not responsive. If you stop your running debugging session, the Vice user interface should become responsive again, right?

Kind regards Roland

[npup]

Hi again, thanks for coming back to me!

The problem is that the VICE monitor never comes alive (trying to start it from VICE), after starting VICE via the extension. It might very well be a problem with VICE itself, but I does not manifest when using VICE on its own so I can't really tell.

Starting the VICE monitor, using it (and quitting from it), using VICE only works as expected.

[rolandshacks]

Hi. I just tried it out again.

Here is what I do:

• Launch vscode, compile, start VICE debugger
• When I try to activate the VICE monitor, VICE freezes
• NOW: Going back to vscode, stopping the debugging session
• VICE unfreezes
• When I now try to activate the VICE monitor, it does what it is expected to do

Is that the same procedure as you are doing?

[fredsa]

Confirmed that VICE will resume after CMD-ESC (in VICE) causes spinning ball, by stopping the current debugging session by either:

1. SHIFT-F5 (in VS Code)
2. Click stop icon (in the VS Code):