Please help testing upcoming openMSX release!

Page 9/11
2 | 3 | 4 | 5 | 6 | 7 | 8 | | 10 | 11

By sd_snatcher

Prophet (3072)

sd_snatcher's picture

24-10-2018, 20:57

New bug report:

The debug_list_all_breaks console command has suddenly disappeared.

When I try the debug_list_all_breaks command on the console, the following error is output in red:

invalid command name "debug_list_all_breaks"

When booting, no error shows up in the console nor everywhere else.

My ~/.openmsx/share/scripts folder has no scripts in it.

How do I bring that command back?

I'm tried to upgrade to the openmsx-0.14.0-372-g54e3e7509-mac-x86_64-bin build, to no avail.

By Manuel

Ascended (15765)

Manuel's picture

24-10-2018, 21:06

Don't you mean the command debug list_bp?

I don't think we ever had debug_list_all_breaks... ah, I see! This command is defined by the debugger, for internal use. So, it's not part of openMSX and even with the debugger, it is not intended to be used outside of it.

See https://github.com/openMSX/debugger/blob/master/src/Debugger...

By Manuel

Ascended (15765)

Manuel's picture

24-10-2018, 21:08

Tolvatar wrote:

May i ask if tsx casete images can be loaded with the new build?
Sorry for my bad english

You may ask of course. TSX cassette images are not supported.
If you want to keep track of this, follow this ticket: https://github.com/openMSX/openMSX/issues/1076

By sd_snatcher

Prophet (3072)

sd_snatcher's picture

24-10-2018, 22:28

Manuel wrote:

Don't you mean the command debug list_bp?

I don't think we ever had debug_list_all_breaks... ah, I see! This command is defined by the debugger, for internal use. So, it's not part of openMSX and even with the debugger, it is not intended to be used outside of it.

See https://github.com/openMSX/debugger/blob/master/src/DebuggerForm.cpp#L834

Seriously? I use the debugger so often that never noticed that. :D

Thanks for the help!

By Manuel

Ascended (15765)

Manuel's picture

24-10-2018, 22:32

Sure, no problem!
Can you confirm the debug break issue with the framerate is fixed?

By sd_snatcher

Prophet (3072)

sd_snatcher's picture

24-10-2018, 22:45

Manuel wrote:

Can you confirm the debug break issue with the framerate is fixed?

Holly cow!!! It's solved!! Thank you all so much for this fix! This bug had been haunting me for years!

Note: also tested the (annoying) function key bug on Mac OS-X and it's still present.

By Manuel

Ascended (15765)

Manuel's picture

24-10-2018, 23:22

Indeed, we didn't do anything about this macos specific issue yet

By sd_snatcher

Prophet (3072)

sd_snatcher's picture

26-10-2018, 00:33

And it's finally fixed!! Thank you all, specially Wouter!

Is it possible to implement this small contribution for the next openMSX version?

Otherwise I have to edit the set2 again and again every time I get a daily build to test (which happens quite often). And for developers it's very useful to have non-obstrusive LEDs always present on screen.

By sd_snatcher

Prophet (3072)

sd_snatcher's picture

28-10-2018, 01:31

Another test result: The CIEL Expert-Turbo machine seems to be broken. It corrupts VRAM data whenever the turbo is activated.

By Manuel

Ascended (15765)

Manuel's picture

28-10-2018, 10:58

When did it get broken? And how to test?

Page 9/11
2 | 3 | 4 | 5 | 6 | 7 | 8 | | 10 | 11