Is there a way to get the stack trace or something similar when using 
the non-debug player.

Generically we will/do get errors from time to time thrown in a running 
application say like index out of bounds or null references or 1009 
errors or some such, although we can catch these errors at a high level 
and display them we cant find a way to display some useful information 
that would then help us locate where the actual error occured.

We cant afford/dont want to go through our entire application and put 
try/catch into every single function. 

Any ideas?  

Reply via email to