> My app has a builtin exception reporting mechanism that sends posts a > log on my web server if my app encounters an unhandled exception, or > other trappable errors. The most important item I capture in that log > is the call stack, so that I know the context of where and when the > issue occurs.
My application has a standardized exception handling routine that includes various bits of information the user can pass on to me so I can figure out what's gone wrong. I would *love* to include at least part of the call stack, so I'm curious if there is an existing method that you use to report the stack, or if it's a roll-your-own thing? - John _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
