|
Post by justnorm on Sept 24, 2018 10:02:24 GMT -5
I need to know how to view the Error Log. Appreciate all help.
JustNorm
|
|
|
Error Log
Sept 24, 2018 10:45:49 GMT -5
via mobile
Post by Rod on Sept 24, 2018 10:45:49 GMT -5
From the fast faq
When your program is executing and comes across an error this is called a runtime error. you will get some form of error report or notice popup, it may simply point you at the error.log. You can look at the error.log by clicking run then selecting error.log. Be aware that the file may be large and that the errors are appended so you need to scroll to the bottom of the file. You may delete the contents or the file, Liberty will reinstate it. The error.log is complex, share it on the forums with the offending code if you want help.
|
|
|
Post by justnorm on Sept 24, 2018 11:38:33 GMT -5
Thanks, Rod. I'll have a look.
|
|
ernie
New Member
Posts: 44
|
Post by ernie on Jun 9, 2020 17:43:03 GMT -5
for some months now LB 4.51 pro has ceased writing to the error.log I've tried deleting the contents of error.log, but it's had no effect my error handler is below. It does trap and correctly report the 55 error
[ErrorHandler] if Err = 3 then msg$ = "RETURN without GOSUB" if Err = 4 then msg$ = "Read past end of data" if Err = 8 then msg$ = "Branch label not found" if Err = 9 then msg$ = "Subscript out of range" if Err = 11 then msg$ = "Division by zero" if Err = 53 then msg$ = "OS Error: The system cannot find the file specified." if Err = 58 then msg$ = "OS Error: Cannot create a file when that file already exists." if Err = 55 then msg$ = "Error opening or saving file - make sure the file you are trying to overwrite is not already open." if Err = 52 then msg$ = "Bad file handle" if Err = 62 then msg$ = "Input past end of file" message$ = "Error detected:"; chr$(13); chr$(13); "Error code "; Err; " - "; msg$; chr$(13); chr$(13); "Check error.log for more information." calldll #user32, "MessageBeep", _MB_ICONSTOP as long, beepResult as boolean : mbflags = _MB_ICONSTOP OR _MB_OK calldll #user32, "MessageBoxA", 0 as long, message$ as ptr, "Psych Reporter" as ptr, mbflags as long, mbResult as long wait
any thoughts or ideas would be appreciated.
|
|
|
Post by metro on Jun 10, 2020 2:57:23 GMT -5
ernie, I happened to see this a while back. Not sure if it's causing your problem You could actually delete the old error.log I believe it will get re-created by LB
|
|
|
Error Log
Jun 10, 2020 3:55:24 GMT -5
via mobile
Post by Rod on Jun 10, 2020 3:55:24 GMT -5
The error.log will just be getting saved somewhere else. Use Windows Explorer, the file icon, to search out all instances of error.log. Remember the last error is at the foot of the file.
|
|
ernie
New Member
Posts: 44
|
Post by ernie on Jun 11, 2020 11:38:34 GMT -5
Thanks, guys. Yes it was in another directory. Found it and all is well. Much appreciated.
|
|