Byond Debugger?

ID:268209
 
Apr 15 2004, 1:07 pm
Hello I was just woundering if a byond debugger that could single step through a byond program was ever made? If not it would be a nice lib for me to download for sure :)
Apr 15 2004, 1:25 pm
What, exactly, do you think it's doing when it tells you "You have X errors"
Apr 15 2004, 1:52 pm
In response to Garthor
Garthor wrote:
What, exactly, do you think it's doing when it tells you "You have X errors"

I mean in real time with like variables and then u can single step through the code too see what each statement of code does.
Apr 15 2004, 3:36 pm
In response to Green Lime
It's just about impossible to do that in a multi-threaded program. You'd have to have a new window for each thread, and even then the behavior would not match what would actually happen.
Apr 16 2004, 7:24 am
In response to Garthor
There are debuggers like that which he is referring to for c++ compilers. When executing your program in debug mode with them it goes one line at a time (You have to press a button to get it to execute the next line), and for times when you need to have it go normal speed so you can get to the part with the bug, you can have change between continuous execution and lin-by-line debugging execution. Those kind of debuggers can be very useful if you do not know how to make up your own debug lines (such as if(hp>maxhp){cout<<"Bug: HP>MAXHP"}).
Apr 16 2004, 7:47 am
In response to Loduwijk
I realize that, but I fail to see how it would work very well in a multi-threaded environment.
Apr 16 2004, 9:06 am
In response to Garthor
I realize that, but I fail to see how it would work very well in a multi-threaded environment.

There is only one thread for the execution of the bytecode. Which is defintely good as if it were multithreaded there would be a whole lot more nasty issues with sharing data between procs.
Apr 16 2004, 10:01 am
In response to Garthor
Delphi (an implementation of Pascal) is multi-threaded, but it has a debugger like this. Alternatively, you could just give the debugger the path to the buggy proc, so it is actually only debugging that thread.