Debugger (vsdbg-ui) crashes on OSX when using 'embedded' symbols
See original GitHub issueEnvironment data
C# Extension version: 1.9 Operating system: OSX
Steps to reproduce
- Create a new console app
- Open the .csproj and add this property:
<DebugType>embedded</DebugType>
- F5
Expected behavior
Debugging works
Actual behavior
Get an error ‘Debug adapter process has terminated unexpectedly’. If you look it crash reporter, you will see, for example that the crash is happening in MakeStream
...
Crashed Thread: 18
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000102031c
...
Thread 18 Crashed:
0 libsystem_malloc.dylib 0x00007fffbbd8f27e malloc_zone_malloc + 103
1 libvsbaseservices.dylib 0x000000010a7d63f8 HeapAlloc + 40
2 libvsdebugeng.impl.dylib 0x000000010ab2c11e MakeStream(unsigned char const*, unsigned int, IStream**) + 46
3 libvsdebugeng.impl.dylib 0x000000010ab03fc8 SymProvider::CDiaLoader::LoadSymbolsForModuleInstance(Microsoft::VisualStudio::Debugger::DkmModuleInstance*) + 312
4 libvsdebugeng.dylib 0x000000010acd3cc2 dispatcher::DkmModuleInstance::FireCreateEvent() + 274
5 libvsdebugeng.dylib 0x000000010acd3acd dispatcher::Clr::DkmClrModuleInstance::Create(_GUID const&, dispatcher::DkmString*, dispatcher::DkmString*, unsigned long, dispatcher::DkmModuleVersion*, dispatcher::Symbols::DkmSymbolFileId*, dispatcher::DkmModuleFlags, dispatcher::DkmModuleMemoryLayout, unsigned long, unsigned int, unsigned int, dispatcher::DkmString*, dispatcher::Clr::DkmClrRuntimeInstance*, _GUID const&, dispatcher::Clr::DkmClrModuleFlags, dispatcher::Clr::DkmClrAppDomain*, unsigned int, bool, dispatcher::Symbols::DkmModule*, dispatcher::DkmModuleInstance::MinidumpInfo const*, dispatcher::DkmDataItem const&, dispatcher::Clr::DkmClrModuleInstance**) + 957
6 libvsdebugeng.dylib 0x000000010acd4175 ProcAEA58B7861C86E08A55546A1C4D0ACAD + 229
7 libvsdebugeng.impl.dylib 0x000000010aa9512c ManagedDM::CDbiCallback::DoLoadModuleImpl(ManagedDM::CClrInstance*, unsigned int, Microsoft::VisualStudio::Debugger::Clr::DkmClrAppDomain*, ICorDebugModule*, Microsoft::VisualStudio::Debugger::DkmModuleFlags, Microsoft::VisualStudio::Debugger::DkmString*, Microsoft::VisualStudio::Debugger::Clr::DkmClrModuleInstance**, ManagedDM::CDMModule**) + 2604
8 libvsdebugeng.impl.dylib 0x000000010aa95d4d ManagedDM::CDbiCallback::DoLoadModule(ICorDebugAppDomain*, ICorDebugModule*, Microsoft::VisualStudio::Debugger::DkmModuleFlags, Microsoft::VisualStudio::Debugger::Clr::DkmClrModuleInstance**) + 253
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Xcode 13.2.1 crashes trying to fetch debugging symbols
1 on my M1 Mac mini (macOS Monterey 12.0.1) crashes immediately while loading a project. The last thing that is displayed in the...
Read more >Debugger crash on symbols load - Visual Studio Feedback
I am attaching crash dump for debugging while trying to debug a native app, it seems it's unable to load symbols. crash callstack:...
Read more >Debugging embedded Lua 5.2.2 code - c++ - Stack Overflow
1 DLL or fails to find required symbols.) If you don't want to compile luasocket, you can get binaries for Windows/OSX/Linux from this...
Read more >Symbol / PDB files in the Visual Studio debugger
Symbol servers you might use include: Public Microsoft Symbol Servers: To debug a crash that occurs during a call to a system DLL...
Read more >How to diagnose and debug embedded software ... - YouTube
Download the CC1312 SimpleLink SDKhttps://www.ti.com/tool/SIMPLELINK-CC13X2-26X2-SDKThis video shows how to use TI's ROV debugger to ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have a PR out in our internal repo. So this should be fixed the next time we insert a new debugger.
@azinoviev Please try installing v1.10.0-beta4 and see if this resolves your issue. See here for instructions.