I followed first the instructions written in this thread " How do I build Notepad++ with Visual C++ 2010 Express? "
Although all the files were compiled successfully when I built notepad++ project on Visual Studio 2010 Ultimate, yet I get this:
First-chance exception at 0x7543b727 (KernelBase.dll) in Notepad++.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0020ff80..
First-chance exception at 0x00000000 in Notepad++.exe: 0xC0000005: Access violation.
First-chance exception at 0x7543b727 (KernelBase.dll) in Notepad++.exe: Microsoft C++ exception: Win32AccessViolation at memory location 0x00210388..
Where could the problem be ?
Are you compiling a Debug build of Notepad++? if so they compile fine with the changes, but crash when starting.
Unicode Release builds (after the modifications you linked to) build and run fine (on express and pro, at least).
Related
I have a Xamarin app for which I have been debugging the UWP app on my computer for testing.
I've been having difficulties debugging. I keep getting a 'No Symbols Loaded' error which goes onto say one of the following errors:
UWPHost.pdb not loaded
or
wkernelbase.pdb not loaded
Typically, restarting or rebuilding Visual Studio will sometimes resolve the issue temporarily. As a result of this, development has been an incredibly painful process.
Any idea how this sort of problem can be avoided?
Additionally, if it's not the PDB errors I get this instead:
Unable to activate Windows Store app ... 'The app didn't start'
These errors can happen with absolutely zero changes.
I'm new to Xamarin so I could be missing something blindingly obvious here.
Something I already tried was checking the 'Microsoft Symbol Servers' option via Visual Studio options.
I'm using Visual Studio 2019.
UPDATE:
I changed the following Visual Studio option:
Tools -> Options -> Debugging -> General -> Enable .NET Framework source stepping
This allowed me to see the following error:
Unhandled exception at 0x7747C762 (KernelBase.dll) in Framework.UWP.exe: 0xE0434352 (parameters: 0x8007000B, 0x00000000, 0x00000000, 0x00000000, 0x03B40000). occurred
The program crashes after 30-45 minutes of operation with the following message:
Exception Thrown at 0xFCA6551 (mfc140d.dll) in WinPDM.exe: 0xC0000005: Access Violation reading location 0x00000008.
The exception occurs when running in both debug mode and from a release build in Visual Studio 2017. The program suddenly shows errors in rendering boxes and buttons, and if one then tries to press a button or select an item, the exception occurs.
The program was originally writtin in Visual C++ 6.0 and ported somewhat successfully to Visual Studio 2017. Many errors were found and removed after running the built-in intellisense analyzer in VS2017, but the exception still occurs. It also occurs in the older versions of the program built in Visual C++ 6.0.
I am looking for suggestions on how to pinpoint where this error is coming from and how to address it.
We have already tried to backtrace using the VS2017 debugger, and also attempted to step into the function call where the exception occurs:
size = m_ShiftList.GetDC()->GetTextExtent(str);
but the debugger refuses to step into the function at this point.
The program can pass through this point with no issues for the first 30-45 minutes of operation. Removing this code (since we can live without knowing the size of the text) moved the same exception to occur at a different point.
When I run a Windows Phone 10 project from Visual Studio 2015 then the following exception pops up after the second run:
Exception thrown at 0x61594533 (WindowsXamlDiagnosticsTap.dll) in remote.exe: 0xC0000005: Access violation reading location 0x00000000.
If there is a handler for this exception, the program may be safely continued.
The exception is raised in debug and release mode. Consecutive runs also fail with this exception. The only fix is to restart Visual Studio after each debug run.
Is there a way to disable this xaml debugging tap? Or what could be the reason for the exception?
Regards,
It might be this known issue: https://github.com/Microsoft/WindowsUIDevLabs/issues/75
Disable Live Visual Tree Debugging as a work around for now.
when I connect sqlserver2013 with vs2013 .net4.0 ,I got the error message:
A first chance exception of type 'System.AccessViolationException' occurred in System.Data.dll
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
We just found that this is the problem of Visual Studio 2013.
"Attempted to read or write protected memory" exception occurs in dubugging mode.
You can switch to VS 2012 or 2010 while waiting for an update.
I'm having trouble with my visual studio 2010. When I open a file and try to edit it, it crashes and gives the following message.
Microsoft Visual Studio 2010 has stopped working.
If I choose to debug, visual studio just-in-time debugger says:
An unhandled Microsoft .NET Framework exception occurred in devenv.exe [2812].
System.InvalidOperationException was unhandled Message: The calling
thread cannot access this object because a different thread owns it.
The following was found in the event viewer:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 6F29B036 (6F250000) with exit code 80131506.
Faulting application name: devenv.exe, version: 10.0.30319.1, time stamp: 0x4ba1fab3
Faulting module name: clr.dll, version: 4.0.30319.296, time stamp: 0x50484aa9
Exception code: 0xc0000005
Fault offset: 0x0004b036
Faulting process id: 0xafc
Faulting application start time: 0x01ce44dbc5e338e5
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio > 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: 09015696-b0cf-11e2-a33a-0023aee722ef
I have tried opening several different file types: xml, aspx, html, vb. They're all causing it to crash. I have run visual studio 2010 in safe mode and opened a single file, outside of a solution and it's crashing before I even edit the file.
It's only started doing this today. I have tried running the repair tool but it has made no difference. I have installed one thing on my machine that may have caused the error. Titanium Studio. Previous to that being installed visual studio 2010 was running okay.
Thanks
Leah
I managed to fix this issue by requesting a hot fix from windows.
Knowledge Base Article: FIX: "Faulting module name: clr.dll" error message when you run a Microsoft .NET Framework 4-based application
Hot Fix Request: DevDiv955340
I had the same error, imediately when Visual Studio 2010 was starting. Only rebooting helped sometimes.
I solved it by removing .NET completely and reinstalling it.
Be aware that if you updated to .NET 4.5 this includes .NET 4, so you have to remove and reinstall .NET 4.5