Different program output when debugged and not debugged, also timing dependent. about sasm HOT 4 CLOSED

@loa-in- No, it prints to the standard output. But when you printed using "PRINT_CHAR bl" and bl was 0, it printed 0 to the standard output. And after it SASM considered that the output is ended. But in the new version of SASM this error was fixed.

from sasm.

Also you have seen unseen before lag (wtf) and the Continue button not doing anything (another wtf). These never occured to me before and were accidentally captured on the recording. There were no pauses during recording, it was all done in one go (as seen on timestamps)

from sasm.

Your program prints zero characters on the standard output. Because of it SASM didn't show it.
But this semi-bug was fixed and now everything should be ok.

from sasm.

Oh, so PRINT_HEX and such print to stderr? I never considered that. Ok then. Thank you.

from sasm.