Zugg Software :: View topic

Posted: Wed Jan 02, 2008 11:13 pm

Admittedly I have a lot of stuff going on when I change rooms, but this all worked great in Zmud. In Cmud it is unbearable. I'm looking at the debugger at what was run and how long it took, but I'm not sure where to concentrate. Can anyone give me some pointers?

I'm a little confused by some of the information given, like what do the letters stand for right after the time stamp and how do I use the timestamps to zone in on the problematic areas? For example I see a blank line with:

0.4441 | a Achaea.m |

Nothing is on there, but it takes 0.4441 seconds to complete. Is that the Mud or is that me?

And on this line:

0.3372 | a Achaea.m #Telnet 200: Room.Brief In the trees above A corridor of flowering plum trees

Does the 0.3372 apply to the whole trigger or just to the detection part. I guess I'm just looking for general feedback to help form a thought process as to how to go about this.

Posted: Thu Jan 03, 2008 7:11 pm

If at a minimum I could get someone to explain what the letters after the timestamp are referring to and what the timestamp measurement boundaries are, I think I could debug this on my own.

There are a couple of ways I could interpret the timestamps:

Method 1
=======
Delta = Time from the end of the last entry including idle time waiting for something to occur. In this case it's difficult to use the timestamps for anything unless you know for certain they are back to back without any idle time included.

Method 2
=======
Delta = Time from the start of execution of this chunk until this code is complete.

If it is using method 2 then this line:
0.4441 | a Achaea.m |

would mean that 0.4441 seconds after the last line completed it received a blank line and finished processing it. Is that accurate? I'm a bit uncertain I'm headed off on the wrong path here.

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

I don't use the debugger but after opening it and having a quick look around I would say the time stamps as you're showing them are delta time stamps, simple showing us the length of time since the beginning of the last message was received by the debugger.
If in the Options menu of the debugger you: check Show timestamps and uncheck Show delta time you'll see the actual time that these events were receieved.
If in addition you check Automatically add seperators whenever nothing happens for a duration of time, ie text received no triggers fire, input received whatever it will put a line showing the timestamp or duration of time that nothing happened.

Also as for what the letters in the 2nd column mean. You can work that out if you try.
notice for example whenever the 3rd column begins with "exec :" the 2nd column begins with a "c",3rd column "Event" 2nd column "m".
With a little effort you could work out a glossary.

Anyways,
Good luck!

Posted: Thu Jan 03, 2008 9:34 pm

"Automatically add seperators" was enabled, but for some reason it is not adding separators. That would actually really help if it did work.

Enchanter Joined: 09 Sep 2007 Posts: 605

Posted: Thu Jan 03, 2008 10:34 pm

Doh, I didn't even see that there... It was right in front of me.

Now I just need to get the "Automatically Add Separators" working and I should be all set to debug this. I tried selecting it and unselecting it, then selecting it again, but it doesn't seem to want to add the separators for me.

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

It wont add it for messages that have already been displayed.
Toggling show delta time stamps option will work on previously Logged debug messages.
However you'll have to debug some more after enabling the auto-sep option.

Posted: Fri Jan 04, 2008 1:34 am

Yeah, I had it enabled the whole time, so it should be working. Does it work for everyone else?

Posted: Mon Jan 07, 2008 8:59 pm

Okay, I finally root caused this to two things which I noted in other topics. One thing I never figured out was an issue with "Automatically Add Separators". I use Cmud on two different computers and with the setting identical on both, it automatically adds separators on one computer but not the other. I can't find any reason why it doesn't work on one computer but works on the other. Quite strange.

Posted: Mon Jan 07, 2008 10:53 pm

The "Automatically add separators" only adds a separator when you enter a new command on the command line. It doesn't add anything when there is just a long delay or anything. Also, it won't add a new separator if one already exists on the last line of the debugger.

You can also send your own separator using the command:

#DEBUG "-"

Posted: Mon Jan 07, 2008 11:04 pm

Thanks, sending my own separator with that command will work perfectly.