Debug your MSX with VSCode

Page 6/6
1 | 2 | 3 | 4 | 5 |

By S0urceror

Master (138)

S0urceror's picture

30-07-2020, 22:06

Briqunullus wrote:

It works great! All I need now is a real project.

Good to hear. Finding a project is the fun part!

By wouter_

Champion (437)

wouter_'s picture

31-07-2020, 17:50

S0urceror wrote:

On Windows not only the socket mechanism is different but somehow it was decided it was a good idea to add enterprise level security as well. Question This complicated the interface with OpenMSX somewhat. Cool

Yeah, that's unfortunate.

On most operating systems we use 'UNIX domain sockets' for the communication between openMSX and external programs. Unfortunately, 15 years ago when we initially added this feature, this mechanism was not yet(*) available in windows. The mechanism that comes closest are regular (local) TCP sockets. However, unlike UNIX domain sockets, these allow connections from any local user (so not just the user that's running the openMSX process). It's possible to send arbitrary Tcl commands over the connection with openMSX, so also stuff like exec del important.doc. Therefor we decided to add this extra layer of security.

(*) Apparently recent versions of windows may now also support UNIX domain sockets. Though this still seems too new to already start depending on it in openMSX :(

By S0urceror

Master (138)

S0urceror's picture

03-08-2020, 10:02

Quote:

Therefor we decided to add this extra layer of security.

Agree extra security is necessary. Another option is using TCP/IP on all platforms with platform neutral security. Something that is portable across platforms. To make OpenMsX clients code similar.

For now no issue because I have it working on Windows (at the expense of having binary bindings with Windows DLLs in otherwise platform neutral Typescript code).

By h0ffman

Supporter (6)

h0ffman's picture

27-10-2020, 13:03

sorry if this is a more vs code related question but I'm hoping someone can help. I've got the debugging setup and working but it requires me to launch openmsx before debugging. The problem is that I'm developing a cartridge and openmsx has a file lock on my binary so I have to keep closing and re-opening openmsx before building / debugging.

Is there a way to configure the launcher to automatically start the emulator and close it when you stop debugging?

By S0urceror

Master (138)

S0urceror's picture

28-10-2020, 07:45

Can you use the commandsAfterLaunch attribute to let openmsx eject and reinsert the cartridge? You can use any command that works in the openmsx console.

By h0ffman

Supporter (6)

h0ffman's picture

28-10-2020, 16:09

Thanks @S0urceror, i'll give that a try.

Page 6/6
1 | 2 | 3 | 4 | 5 |