Hi Maggie, Firstly can I suggest you download the latest production version of the Witango Server - 5.0.1.065. There were number of issues fixed between .062 and .065 and some did cause crashes.
I think Alan has correctly shown how to display the name and values of variables in a particular scope. There is also a component on the component zone of witango.com entitled 'Show all arguments and variables' which also demonstrates how to do this. Can you look in the witangoevents.log file (located in your configuration directory) and see if anything is being written when the crash occurs. If this does not reveal anything, can you check your witango.log file. Note also that you may want to increase the logging level (set in witango.ini) so that more information is returned. This will give you the ability to see what was going on in the lead up to the crash without having debug switched on. I hope this helps and if I can assist you further please do not hesitate to contact me. Fergal Fergal Donlon Witango Technologies, Suite 4, Level 1, 44 Miller Street, North Sydney, 2060 ----- Original Message ----- From: "MJPinckard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, July 16, 2004 11:10 AM Subject: Witango-Talk: Returning all variables within a scope > What would the syntax be to capture all the variables in a specified > scope (e.g in the manner that the debugging prints all "request" and > "user" variables to screen)? > > I'm having an intermittent problem, and I'd like to log the user's > variables when the problem occurs, so I can identify the problem. My > thought is to capture variables whenever the error conditions are met > during the next few weeks (the testing period before go-live on this > code). My testers don't normally have debugging turned on, and if I turn > debugging on and reload the screen, the intermittent problem clears, so > I can't get details. > > I'm looking for something along the lines of <@PURGE scope="request">, > only to print, not purge. I tried <@var scope="request"> but it didn't > work. > > "Well it works for me" and "just reload, it'll go away" while accurate, > is not satisfying to my users. > > Thanks for your help. > > Maggie Pinckard > ============= > Principal Research Associate > Enduse Forecasting > Lawrence Berkeley Laboratory > [EMAIL PROTECTED] > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
