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.
More Related Contents:
- How do I remedy “The breakpoint will not currently be hit. No symbols have been loaded for this document.” warning?
- Display lines number in Stack Trace for .NET assembly in Release mode
- Why does .NET add an additional slash to the already existent slashes in a path?
- Can’t view designer when coding a form in C#
- Performance differences between debug and release builds
- The name ‘ConfigurationManager’ does not exist in the current context
- Cannot step into .NET framework source code
- Don’t stop debugger at THAT exception when it’s thrown and caught
- Combining multiple Attributes to a single Attribute – Merge Attributes
- How can I embed an application manifest into an application using VS2008?
- User Activity Logging, Telemetry (and Variables in Global Exception Handlers)
- Can the C# interactive window interact with my code?
- Cannot find .cs files for debugging .NET source code
- How to create trial version of .NET software? [closed]
- Passing command line parameters with Visual Studio C#
- Visual Studio 2013 doesn’t discover unit tests
- System.BadImageFormatException: Reference assemblies should not be loaded for execution [duplicate]
- How can we change the background color of all other forms from one form?
- How can I include line numbers in a stack trace without a pdb?
- Create web service proxy in Visual Studio from a WSDL file
- Visual Studio – project shows up as “Miscellaneous Files”
- Symbol file not loading for debugging custom project in Visual Studio 2012
- Visual Studio 2015 RTM – Debugging not working
- streamWriter rewrite the file or append to the file
- Get types used inside a C# method body
- How to create an installer for a .net Windows Service using Visual Studio
- Trace vs Debug in .NET BCL
- Visual Studio 2015 diagnostics tool does not support current debugging configuration
- C# tutorial to write gadgets
- Should I compile release builds with debug info as “full” or “pdb-only”?