ID:163021
 
throughout my time on byond ive slowly recieved more and more methods of catching cpu usage and bugs.

the first thing was profile cpu reports. Which i didnt learn till years after starting here.

The second was .debug which i still dont use enough.

Im curious as to what options there are for finding the source of things like lag spikes and bugs that cause stuff like crashing or server locking up. What tools are available that I may not know about? Is there debug functions in byond that give detailed crash reports if the game goes down? Who has some experience with this? Is there a debug version of byond to run to give admins better bug reports?
Masterdan wrote:
Im curious as to what options there are for finding the source of things like lag spikes and bugs that cause stuff like crashing or server locking up. What tools are available that I may not know about? Is there debug functions in byond that give detailed crash reports if the game goes down? Who has some experience with this? Is there a debug version of byond to run to give admins better bug reports?

Try typing ".debug trace-client" (I believe this still works in 4.0 through the O&M dialogs/command option). That will produce a file called "trace.txt" in your cfg directory. It will indicate code points before crashes, which sometimes helps us out.
In response to Tom
am i able to do this while running a server on a linux machine in DreamDaemon? if so how?