Program and debugger quit without indication of problem

Question

Program and debugger quit without indication of problem

I'm developing a WPF application. When debugging, the logic reaches a certain point, then the application quits for no reason. VS debugger catches nothing and the only indication of a problem is the following in the output window:

The program '[6228] SomeApp.vshost.exe: Managed (v4.0.30319)' has exited with code 1073741855 (0x4000001f).

When debugging the release version, or indeed running the debug build out of the debugger (in fact all combos that aren't running the debug version in debugger), everything works fine.

I'm trying to catch unhandled exceptions with the following code:

        AppDomain
            .CurrentDomain
            .UnhandledException +=
            (sender, e) =>
            {
                Debug.WriteLine("Unhandled Exception " + e.ExceptionObject);
            };
        Application
            .Current
            .DispatcherUnhandledException +=
            (sender1, e1) =>
            {
                Debug.WriteLine("DispatcherUnhandledException " + e1.Exception);
            };

...but I'm not catching anything.

I'm considering peppering the app with debug output statements, but it's highly asynchronous so reading this will be both arduous and tedious.

How do I start figuring what is going on?

c#

.net

visual-studio

debugging

asked on Stack Overflow Dec 26, 2010 by

spender • edited Aug 17, 2019 by

Dharman

6 Answers

According to ntstatus.h file, 0x4000001f (STATUS_WX86_BREAKPOINT) is an exception status code that is used by the Win32 x86 emulation subsystem. It (I suppose) means that you reached a breakpoint which is not exploitable. You should enable debugging unmanaged code.

answered on Stack Overflow Dec 26, 2010 by

Vladimir

Using Visual Studio 2012 (Version 11.0.50727.1 RTMREL), the only solution I found was to go to Project -> Properties -> Debug and turn off "Enable the Visual Studio hosting process".

The option "Enable native code debugging" did not help even though I had all exceptions set to break-when-thrown.

Interestingly, this problem only started happening when I upgraded from VS2012 beta to the VS2012 official release.

answered on Stack Overflow Sep 12, 2012 by

Ron

I Have the same Situation with Visual Studio 2013. Like Ron This save My day : Project -> Properties -> Debug and turn off "Enable the Visual Studio hosting process".

Thanks

answered on Stack Overflow Mar 2, 2015 by

PachecoDt

Rebooting fixed the problem for me.

I encountered the problem attempting to debug through NUnit via Resharper's test runner, and separately attempting to step through a W3WP.exe process.

answered on Stack Overflow Mar 23, 2015 by

Peter Seale

I was experiencing the same problem . in my case I noted I had a property with getter and setters . My mistake was to return the property itself instead of the attributed linked to it, and this was forcing the debugger to go to an infinite loop , after fixing , the problem was solved . I was getting the same error code with no additional info-

answered on Stack Overflow Feb 19, 2015 by

Siamak Rahimi

I was getting the same behavior with FonstSize="auto" (not sure why):

<TextBlock Text="{Binding DisplayText}" FontSize="auto"/>

Fix:<TextBlock Text="{Binding DisplayText}" />

Additional Error Output:

LS stop assert - tserrInternalError, file f:\dd\wpf\src\native\ums\shared\inci\tsoverflow.h, line 66

An unhandled exception of type 'System.Exception' occurred in PresentationCore.dll Additional information: Vom Textformatierungsmodul kann aufgrund des folgenden Fehlers keine Textzeile formatiert werden: "LsInternalError".

answered on Stack Overflow Nov 13, 2018 by

FrankM

User contributions licensed under CC BY-SA 3.0