Documentation for command-line debugging?

Is there any documentation that describes how to use and interact with the simulator for debugging?

Out of both curiosity and personal preference (VSCode vs. Eclipse) I'd like to see if there's a way the debugger can be integrated with VSCode as an extension.

FlowState over 5 years ago

This may be of interest (it's a request to port over the MonkeyC plugin to an IDE other than Eclipse)

github.com/.../14

PUFFOLINO over 5 years ago in reply to FlowState

Would also like to have more information here,, but I have already wrutten the windows tool screeny which does control the compiler and the simulator as well as any text editor, so you don't need eclipse for writing an app for your watch.

nilsbenson over 5 years ago in reply to FlowState

I can use this in combination with the MonkeyC language server extension to get syntax + build & deploy working to the simulator in VSCode which will be at least part of the battle. I may have to resort to wireshark sniffing on the communication to the simulator to figure out how to communicate with it for a debugging session which I don't really want to do.

nilsbenson over 5 years ago in reply to PUFFOLINO

Does screeny actually allow for debugging (stepping, breakpoints, variable interrogation)?

I can integrate the build and deploy steps but it's the debugger protocol I want to know about. The mock debug adapter for VSCode lays out everything you need to integrate something and I'm looking at either having to sniff all the traffic between eclipse and the sim, or figuring out how to use the .jar to manage a debug session.

I cracked open the jar in a disassembler and I can see where all the debug stuff happens but there's no clear way to see the order of operations / etc without figuring out how to debug the plugin in Eclipse.

It's pretty clear that the shell is used to connect, and the shell provides multiple streams/sessions (debug output, debug commands I'm assuming). I can replicate some of the connection and starting the session from the command line but when you try to enter a CIQ session it stops updating the screen because I assume it's wanting to be used as multi-session.