|
|
Post by scotty2006 on Aug 31, 2006 17:53:53 GMT -5
When I run a program directly in LB v4.03 it works fine. However when I run the same code through LBW nothing happens for a while and then I get an error box with title "Smalltalk/V" that says "Virtual machine stack overflow".
Any idea what's going wrong, or what I haven't set up properly, and how to cure it.
Thanks. - I'm very new to LBW
Bob
|
|
|
|
Post by JohnDavidson on Sept 1, 2006 1:46:27 GMT -5
Hello Bob
You might want to check the path to Liberty BASIC in the options window.
I have had problems when the LB version specified was older than the version the Bas file was written in.
John
|
|
|
|
Post by scotty2006 on Sept 1, 2006 4:13:12 GMT -5
John,
Thanks for your response. The program was written this week in LB v4.03 so I don't think it's a version problem. I think I've set up the path properly (LBW seems to be finding LB ok) but I will check the path settings again.
Bob
|
|
|
|
Post by Alyce Watson on Sept 1, 2006 5:34:27 GMT -5
LBWorkshop and all add-on editors write a file to disk, then run Liberty BASIC with the filename as a commandline parameter. After that, it's up to Liberty BASIC to handle things. The way LB performs when running code from the commandline seems to change as LB is updated.
I wish I could guess at what is causing the problem. Have you tried running for debug? Have you tried tokenizing your code and running it with the runtime engine?
|
|
|
|
Post by scotty2006 on Sept 1, 2006 17:30:48 GMT -5
Alyce,
thanks for your response. Please could you explain what you mean by "running for debug" - also, are you referring to the function using LB directly or from LBW? Using LB alone I have in fact created an Application from the code and the .exe file runs fine. I don't know whether this covers your question about tokenising and running with the runtime engine, or whether they would involve other parts of the software?
Bob
|
|
|
|
Post by Alyce Watson on Sept 2, 2006 7:25:39 GMT -5
Bob, yes, I was asking if you tokenized and ran as an executable, outside of the LB editor.
To run for debug, use the "Liberty BASIC" menu in LBW, and instead of activating "Run Active Code", activate the "Debug" menu item. This calls up LB with the debugger window active. You must then run the code in the LB debugger. It won't run automatically. It will run until it encounters and error, and then the line of code which caused the problem should be highlighted. Also, the caption of the debugger window will contain an error message.
I'm really at a loss to know what the problem is. It must be a subtle problem inside of LB and the way it runs from the command line. All LBW does is write a temporary file to disk and ask LB to run it, so there should be no difference at all in the actual code.
|
|
|
|
Post by scotty2006 on Sept 14, 2006 11:48:21 GMT -5
Thank you both for your help and suggestions. I have cured the problem by reinstalling LB v4.03 and setting up the paths again in LBW and everything is now working fine (no, I don't know why either!).
I've only used a tiny fraction so far of what LBW can do, but it's a great program, Alyce. Thanks,
Bob
|
|
|
|
Post by Alyce Watson on Sept 14, 2006 12:58:41 GMT -5
Thanks for your kind words! ;D
|
|
