Debug your MSX with VSCode

Страница 5/7
1 | 2 | 3 | 4 | | 6 | 7

By Briqunullus

Champion (408)

Аватар пользователя Briqunullus

20-07-2020, 22:39

I still get an "Error connecting to OpenMSX" when I hit F5. Tried a couple of thing to solve this, but to no effect. Any tips?

OpenMSX is open and running. The bin directory is selected as drive A. I can bload,r my sample program, I just can't start a debug session.

By S0urceror

Master (187)

Аватар пользователя S0urceror

20-07-2020, 22:45

Briqunullus wrote:

I still get an "Error connecting to OpenMSX" when I hit F5.

This is the message saying Dezog cannot connect or cannot find the OpenMSX socket. What is your OS? OpenMsx version?

I am running on Mac so I still need to test on different OSes.

By Briqunullus

Champion (408)

Аватар пользователя Briqunullus

21-07-2020, 08:51

I'm with OpenMSX 0.15.0 on Windows 10.

By S0urceror

Master (187)

Аватар пользователя S0urceror

21-07-2020, 18:01

Ok, I’ll check on Windows tonight.

By Grauw

Ascended (10066)

Аватар пользователя Grauw

21-07-2020, 19:13

I tried it and it’s connecting and generally working (macOS btw).

However when I try to set a breakpoint I get this error in the debug console:

Unverified breakpoint:{"verified":false,"line":71,"column":0,"source":{"name":"Player.asm","path":"/Users/grauw/Development/gngplay/src/Player.asm","sourceReference":0}}

Any idea what that could be about? I used the filter for Glass.

By Manuel

Ascended (18157)

Аватар пользователя Manuel

21-07-2020, 19:21

Connecting works differently on Windows, because it doesn't support UNIX domain sockets. More details in the documentation.

By S0urceror

Master (187)

Аватар пользователя S0urceror

21-07-2020, 19:24

Grauw wrote:

Any idea what that could be about? I used the filter for Glass.

Is the path mentioned okay? If not check the root folder.

Otherwise it is Dezog not recognizing the source file as part of the project. It should be part of the list file and marked as an include. I know that sjasmplus uses + symbols to show how deep an include is nested. I checked yesterday with 1 include on Glass and it worked.

Also note that Dezog might not understand your special directives and macros. I know it does special things with these on sjasmplus.

Without your code it is difficult to make a complete assessment. You can PM me if you want me to dig deeper.

By Ped7g

Resident (36)

Аватар пользователя Ped7g

23-07-2020, 13:00

Grauw wrote:

Cool, I had seen your previous message before you edited it, so I thought I could make the output a bit more compact and robust, and secretly also a little more similar to Sjasm’s output although that certainly isn’t a design goal Smile.

JFYI (I = inspiration? Smile ):
sjasmplus current listing supports fixed-column way to make parsing in some ways simpler (and more difficult in other), so:
* the lines beyond max line number (99999) goes further in the ASCII (100k = ":0000")
* after the line number there're include-depth indicators (if they fit into the 6-char column reserved for line+depth)
* the addresses are truncated to four digits only (0000-FFFF) (I'm not really happy about it, but delaying the change to lst format to some larger version change)
* the machine code bytes are limited to four per line, longer blocks are split over multiple listing lines or using elipsis "..." in certain situations, not listing all of the bytes.
* the single char ahead of assembly source can mark also line emitted by macro ">" or skipped due to conditional assembling "~"

Overall there are many subtle details and corner cases, but checking the tests files it seems the listing stuff is not nicely grouped together, but scattered through the hundreds of tests, so I can't easily point you to some full-like examples of what listing files do, maybe one non-trivial is https://github.com/z00m128/sjasmplus/blob/master/tests/misc/...

If you have particular dilemma and are curious how sjasmplus does it, let me know (maybe github ticket on sjasmplus so I find it quickly, I'm reading the MSX forum only once in couple of days). It may be not a good fit for your Glass, but it may give you inspiration how to not do it. :D Cheers.

By S0urceror

Master (187)

Аватар пользователя S0urceror

30-07-2020, 17:46

Briqunullus wrote:

I'm with OpenMSX 0.15.0 on Windows 10.

I created a new Dezog release. This release now also supports OpenMSX on Windows.

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

Nevertheless, this is fixed now. Have fun debugging on Windows!

Install it by running:

code --install-extension dezog-1.3.5.vsix

You''ll find it here.

By Briqunullus

Champion (408)

Аватар пользователя Briqunullus

30-07-2020, 19:19

Thanks for your hard work. It works great! All I need now is a real project.

Страница 5/7
1 | 2 | 3 | 4 | | 6 | 7