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 / Problems with debugging.

Author
Message
TonyP
22
Years of Service
User Offline
Joined: 23rd Sep 2003
Location:
Posted: 29th Oct 2003 14:11
Has anyone else experienced problems when debugging after using the latest patch? I have recently started having problems with the debugger crashing whenever I try to enter the 'watch' window. I tried reinstalling everything but still happens.

WinXP, P4-3.06, 1 gig mem, GForce4fx
STE
22
Years of Service
User Offline
Joined: 7th Oct 2003
Location:
Posted: 29th Oct 2003 14:28
Yes, same here. I have always had this problem.

I can't seem to use the built in debugger at all. The stupid thing is always crashing. Variable watch seems to be particually dodgy.

I print my variables to screen instead - not the best way to develop software.

Win98, Tbred2400+, 512MB, 9800Pro

STE ;¬!
CattleRustler
Retired Moderator
22
Years of Service
User Offline
Joined: 8th Aug 2003
Location: case modding at overclock.net
Posted: 29th Oct 2003 18:03
same here, the debugger stinks unfortunately - I do the same...debug print to the game surface-lame!

-RUST-
BatVink
Moderator
23
Years of Service
User Offline
Joined: 4th Apr 2003
Location: Gods own County, UK
Posted: 29th Oct 2003 20:45
Another "Aye" to a crashing debugger...thought it was just me!

BatVink (formerly StevieVee)
http://facepaint.me.uk/catalog/default.php
Rob K
Retired Moderator
23
Years of Service
User Offline
Joined: 10th Sep 2002
Location: Surrey, United Kingdom
Posted: 29th Oct 2003 20:54
I send fairly regular emails to Lee about this. I'm hoping that if enough people express their issues with it then they will be fixed in the next update.

[email protected]

Rob K
Retired Moderator
23
Years of Service
User Offline
Joined: 10th Sep 2002
Location: Surrey, United Kingdom
Posted: 30th Oct 2003 12:47 Edited at: 30th Oct 2003 12:48
Quote: "does the blue IDE have that problem? or is that integrated into the compiler? How long before the DB Staff actually hire Knight and release the blue IDE?"


Unlike Visual Basic / Delphi / VisualC++ The debugger is seperate from the IDE. Lee coded the debugger.

You can look at the IDE code for yourself, all it does in debug mode is write CLI=YES to the project file, which causes the compiler to start the debugger.

Third party developers don't have enough access to code a debugger as it requires very tight integration with the compiler.

Quote: "Will Blue also support DBC? or just DBPro?"


Just DBPro at the moment. It wouldn't be hard to make it DBC compatible though.

thedubdude
23
Years of Service
User Offline
Joined: 24th May 2003
Location: San Jose, Ca.
Posted: 31st Oct 2003 22:27
I have lots of difficulty with the de-bugger. The variable watch only works about 10% of the time (I reported it as a bug but they couldn't duplicate it). The command line interface crashes if you try to do just about anything with it. The only use I've found for the debugger is in step through mode. Mr. Knight sent me a debug utility that helps bunches. It allows you to print anything to a sepreate window. You insert the equivalent of print statements in the program and they get printed to a de-bug window which is seperate from the main window.

I really hope the debugger is re-written as it is such an important function.
Rob K
Retired Moderator
23
Years of Service
User Offline
Joined: 10th Sep 2002
Location: Surrey, United Kingdom
Posted: 31st Oct 2003 23:14 Edited at: 31st Oct 2003 23:15
In case anyone else wants here is the debuglog utility:

http://blueide.sf.net/dl/debuglog.zip

It's pretty simple atm.

ENABLE DEBUGLOG (enables writing to debug file)
DEBUGLOG string (writes debuglog entry)
DISABLE DEBUGLOG (disables writing to debug file - use this when compiling for release)
CLEAR DEBUGLOG

A little helper program is started when ENABLE DEBUGLOG is called which displays the log so you can view it whilst developing.

CattleRustler
Retired Moderator
22
Years of Service
User Offline
Joined: 8th Aug 2003
Location: case modding at overclock.net
Posted: 31st Oct 2003 23:45
cool, a little debug-output window. Now maybe dbp could have Try-Catch-Finally-End Try blocks?

-RUST-
Batty
22
Years of Service
User Offline
Joined: 26th Oct 2003
Location:
Posted: 1st Nov 2003 06:35
I had this problem also and found that it seemed to be when the debugger was trying to print an empty string. When I initialized all my strings to " " right at the beggining of my program everything has been fine since.
thedubdude
23
Years of Service
User Offline
Joined: 24th May 2003
Location: San Jose, Ca.
Posted: 1st Nov 2003 22:14
Thanks Robert for posting your great de-bugging tool for all to have. One comment/question....is it possible to increase the amount of text that can be written to the de-bugger window. I am constantly bumping into this....where it says I've exceeded the capacity of the window and outputs nothing as a result. Thanks.
Rob K
Retired Moderator
23
Years of Service
User Offline
Joined: 10th Sep 2002
Location: Surrey, United Kingdom
Posted: 2nd Nov 2003 01:52 Edited at: 2nd Nov 2003 01:54
Are you running Windows 98 or XP dubdude?

On Windows 98 textareas have a limited size (of 64K I think). On XP the space is unlimited.

thedubdude
23
Years of Service
User Offline
Joined: 24th May 2003
Location: San Jose, Ca.
Posted: 2nd Nov 2003 04:32
Windows 98....So I guess that explains it . Thanks.

Login to post a reply

Server time is: 2026-07-26 08:30:46
Your offset time is: 2026-07-26 08:30:46