[Mono-bugs] [Bug 669836] New: Unhandled exceptions thrown in threads other than the UI thread aren't caught by the debugger

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=669836

https://bugzilla.novell.com/show_bug.cgi?id=669836#c0


           Summary: Unhandled exceptions thrown in threads other than the
                    UI thread aren't caught by the debugger
    Classification: Mono
           Product: MonoDroid
           Version: unspecified
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Debugger
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: matware at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Customer
           Blocker: No


Description of Problem:
When debugging on a device (Desire HD) if the application throws an exception
in a thread other than the UI thread the debugger don't catch and display the
unhandled exception.

This is a major PITA when trying to diagnose cross thread invoke issues as
attempting to update a UI component from a non-UI thread will just cause the
application (and debugger) to exit with no information about what happened.


Steps to reproduce the problem:
1. Create a simple application with a text edit field call myTextEdit.
2. ThreadPool.QueueUserWorkItem(
        delegate()
        {
           myTextEdit.Text = "This should explode and get caught by the
debugger";
        }


Actual Results:
The application exits with no diagnostic information, the debug session ends.

Expected Results:
The debugger will catch the unhandled exception and show me that the
application has thrown an unhandled InvalidOperationException.

How often does this happen? 
Always

Additional Information:

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.