Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

DarkBASIC Professional Discussion / DarkBASIC Pro Error Messages

Author
Message
mike01082
13
Years of Service
User Offline
Joined: 2nd Dec 2012
Location:
Posted: 2nd Dec 2012 18:37
Do you have a newer version of darkBASIC Pro that gives you the exact line number when you get an error?

Thanks, Mike
TheComet
18
Years of Service
User Offline
Joined: 18th Oct 2007
Location: I`m under ur bridge eating ur goatz.
Posted: 3rd Dec 2012 00:18
DBP will give you the exact line number. The only time it won't is with nesting errors (if you forgot an endif for example), and from what I can gather about compilers it's not possible to determine the exact line number with those kinds of errors.

TheComet

MrValentine
AGK Backer
15
Years of Service
User Offline
Joined: 5th Dec 2010
Playing: FFVII
Posted: 3rd Dec 2012 01:41 Edited at: 3rd Dec 2012 01:42
Often you would create a debugger internally which would catch the errors and output a relavent error log, alternatively, you could use an event log file and attempt to figure out where it went wrong from that...

I would say have a look at STYX for its error trapping, Matrix1utils may feature a similar function.

Quote from STYX:
Quote: "
Runtime Error Handling and Anti-Aliasing

Handle a wide range of runtime errors in your DarkBASIC Professional application. So you can prevent the program from terminating if you load corrupted media files for example. The latest version of STYX allows you to control the anti-alias settings of your 3D scenes, too.
"


Quote from Matrix1Utils:
Quote: "
06 - Error message control - Take a little control over DBPro error messages, or even trigger your own (with a line number!)
"


Hope that helps...

EDIT

OH AND WELCOME to the Forums mike01082

Jambo B
16
Years of Service
User Offline
Joined: 17th Sep 2009
Location: The Pit
Posted: 3rd Dec 2012 18:57 Edited at: 3rd Dec 2012 18:57
I believe there is also a problem with REM statements in case statements:



I think this is right!

James
Ortu
DBPro Master
18
Years of Service
User Offline
Joined: 21st Nov 2007
Location: Austin, TX
Posted: 4th Dec 2012 01:49
Using #include can give some wonky line numbers as well. I usually have it write out a txt debug file to track own what's going on if it's crashing or print to screen if something just isn't working right

Login to post a reply

Server time is: 2026-07-07 09:28:19
Your offset time is: 2026-07-07 09:28:19