Fatal error in JustBasic that crashes the editor: "is empty"

[Elora]

I have been using JustBasic for a very long time, and there is a persistent error caused by Every combination of code that happens completely randomly, at least a couple times in a day.

  While testing Any program written in Just Basic, the program will suddenly close and open a window that says that the error is this "is empty", and when this particular error happens, the data in the editor is corrupted and there are huge blank spaces where the code should be.

  Needless to say that I have long since developed the habit of saving before each and every run, because of the constant chance that this will happen.

  I'm posting this to ask what this error is and what causes it, no more, no less.

Attachments:

[tsh73]

I use JB since 2007
It always have been a reason to crash - or I would abandon it long ago, really.

and yes I habitually save file before run since old DOS days.

(just to remind, there is also
Setup \Preferences\save *BAK file on run/debug
option)

So.
1) Does it breaks on examples shipped with JB too?
2) Have you looked into error.log, as error message suggests?
If you post last part of error.log folks sometimes could explain what it complains to.
(there is a help topic "Error Log Explained" too)

[Rod]

Is Empty is an error code that is to do with bad program flow or bad syntax. But your code has created an error that the syntax check or the runtime check cannot put in a "box". Most often it is to do with missing info in a command line. Just BASIC is expecting info and does not get it. If it happens "randomly" it is because the command line at fault gets called occasionally.

I used to get "is empty" often, but as my skills in Just BASIC improved it faded into the background.

The debugger, the ladybug icon, is capable of halting on the offending line if you multistep or run within the debugger.


The error.log will give further clues.



Oh, and please stop shouting at us with your bold type, its rude.

[Elora]

Bold type is intended to emphasize that a certain detail is Unconditional and it is completely acceptable in the way I have used it, correctly so. So stop your personal attacks on my writing style, that is Unconditional!   You need to value respect for people over your need to collect new code from them, that pushes people away, if you intend to push people away, the forum will go nowhere, good luck with that!

It's possible that some program flow trips up, but I can test every single feature in my program several times and not run into the problem, and am assured that every single line is executed correctly. Other times, some combination of things trips up, and maybe it has something to do with what you have mentioned, but it is not the case that certain code causes it every time, or I would have a much different pattern of crashes.

[Rod]

Can we see the error.log? This should give us a better handle on why you get the crash. It builds over time, you can delete it and Just BASIC will rebuild it. If you can find a recent entry post it here, if not run till the next crash and post it.

[Rod]

Also a question, do you have several instances of the editor open at the same time? I often do but I am careful to name each file I am working on uniquely. Version 1 version2 etc. I am thinking that this is an unusual error and I can't recall it being reported before. So guessing I would postulate that you have more than one instance of the editor running working on the same file name? Just a long shot guess.

[carlgundel]

Nov 26, 2018 8:44:28 GMT Rod said:

Can we see the error.log? This should give us a better handle on why you get the crash. It builds over time, you can delete it and Just BASIC will rebuild it. If you can find a recent entry post it here, if not run till the next crash and post it.

I agree that the error.log should be helpful.