Please help testing upcoming openMSX release!

Page 64/65
57 | 58 | 59 | 60 | 61 | 62 | 63 | | 65

By MsxKun

Paragon (1100)

MsxKun's picture

18-05-2022, 19:07

Didn't try anything more. Didn't code more than 5 mins in days. Crying
Also, on the minipc it takes some hours to compile the openmsx source, so not going to do it daily.

By Manuel

Ascended (18779)

Manuel's picture

19-05-2022, 00:40

Well, there aren't daily changes. Especially not now, just before a release Smile So just a recent version is already very useful to try out.
Also, ever thought about cross-compiling? Smile

By mcolom

Master (241)

mcolom's picture

19-05-2022, 09:43

It works nicely for me Smile
The only problem I've seen with the very last version in github, is that before I could attach two openMSX processes to two different debuggers (it's useful to figure out why a programs works in one machine and not in others), but now the second debugger does not attach if there's another one already running. It simply does nothing when clicking on "connect".

I don't know if it's because of a change in openMSX or the debugger, or something else, though.

By Parn

Paladin (781)

Parn's picture

19-05-2022, 14:45

Pretty satisfied with things so far. I was playing Scramble Formation the other day with the arcade music mod. Really didn't remember how this game is such a flickerfest. Nothing wrong with OpenMSX, of course.

By MsxKun

Paragon (1100)

MsxKun's picture

19-05-2022, 15:29

Manuel wrote:

Also, ever thought about cross-compiling? Smile

Yes but I don't wanna mix things on main computer, specially config files that proved to be not totally compatible on the newer version, and don't wanna them duplicated, plus duplicated machines... I have some special one without boot logo just to use as a PT3 player. I know there's a PT3 player and it works on linux too, I use it, but I wanted to add more formats and stuffs... Sometimes it's only because "why not".

Also, ever thought about AppImage? Tongue

By Bengalack

Hero (578)

Bengalack's picture

21-05-2022, 08:26

Not sure if this is related to the emulator or the debugger, but for a long while, and still present in the later 17-builds, is that the debugger often is unable to connect to openmsx if you have a tcl-script running. I often have a profiler-script or the vars.tcl-script running. In many cases, when attempting to connect the debugger, I get an eternal windows-rotating-circle. Sorry, but I haven't reported this earlier. The reason is that, as I have found a workaround, I haven't really dug too deep into it - as often is what you should do when reporting, so that devs can fix things quickly.

This might be known? The current workaround is to just not load the scripts Smile

By wouter_

Champion (484)

wouter_'s picture

21-05-2022, 10:29

Hi Bengalack,

What do you mean with "a Tcl-script running". Do you mean (continuously) actively executing. Or only (from time to time) reacting to events. If there is a continuously running Tcl script, then indeed openMSX won't accept new debugger connections. But then also openMSX won't have a chance to perform any actual MSX emulation.

Can you share the offending script?

By Bengalack

Hero (578)

Bengalack's picture

21-05-2022, 15:39

wouter_ wrote:

Hi Bengalack,

What do you mean with "a Tcl-script running". Do you mean (continuously) actively executing. Or only (from time to time) reacting to events. If there is a continuously running Tcl script, then indeed openMSX won't accept new debugger connections. But then also openMSX won't have a chance to perform any actual MSX emulation.

Can you share the offending script?

Ok, that explains it. The script I'm using is this from Grauw:
https://www.msx.org/forum/msx-talk/openmsx/performance-profi...

and with my accompanying settings for it, it surely was running and measuring timings at the time I was trying to hook up the debugger. The first time I encountered this, was during a time I used the profiler script default on as part of my run-script. Profiler "always on", so I was a bit blinded by this, and spent a lot of time figuring out why the debugger wouldn't connect. If possible and for future users it would be nice if some kind of specific info could be presented to the user when this occurs :)

By Manuel

Ascended (18779)

Manuel's picture

21-05-2022, 17:46

As Wouter said, when a script is actively executing, no emulation takes place. So, I wonder what is going on with that script...

By Grauw

Ascended (10577)

Grauw's picture

21-05-2022, 18:52

My profiler script works on breakpoints so it’s definitely not always executing.

In a number of my projects I have it running every time I test, and I don’t recall any debugger connection problems…

Page 64/65
57 | 58 | 59 | 60 | 61 | 62 | 63 | | 65