I have a c# application I've developed and am trying to put into production. The published version will periodically crash with an unhandled Stack Overrun exception.
I would like to do a desktop sharing session, reproduce the crash, and have you help configure the debugger to return a meaningful stack trace. The goal is to find the line of code that is causing the crash. I'd like to do this sometime between 10am - 11am Central Standard Time tomorrow (tuesday).
I know this sounds easy, but I'm relatively new to .net, and am stumped. I've tried to attach Visual Studio to the process to debug the problem, but the debugger only gives me assembly code, and I can't interpret the stack trace. I think I may not have the required "Symbols" loaded to properly debug. This may be as simple as demonstrating proper use of the debugger, or it may end up being more difficult.
## Deliverables
I want you to identify in my source code which line is causing the unhandled exception.
We'll do a desktop sharing session (preferably using [login to view URL]), I'll reproduce the problem for you, and show you my difficulty in using the debugger to identify it. You'll show me how to properly use the debugger to identify the line causing the crash.
During this we'll either be using Instant Messenger or talking on the phone (international callers will have to initiate the call from their end).
Success means we've positively identified the source of the error (not the underlying reason, just what line is throwing the exception).
## Platform
Microsoft windows XP
Visual Studio 2008 Professional Edition
C# - Windows Forms application