Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Debug adapter process has terminated unexpectedly" on certain pages. #1504

Closed
guidobouman opened this issue May 22, 2017 · 4 comments
Closed

Comments

@guidobouman
Copy link

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.1)

Product Information:
 Version:            1.0.1
 Commit SHA-1 hash:  005db40cd1

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/1.0.1

VS Code version: 1.12.2
C# Extension version: 1.9.0

Actual behavior

When starting a dotnet core 1.1 debugger, the process spins up like it should. Certain pages from our web project I can visit. But visiting others will make the debugger crash with Debug adapter process has terminated unexpectedly

Expected behavior

A working debugger.

Settings

launch.json:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "PROJECTNAME",
            "type": "coreclr",
            "request": "launch",
            "program": "${workspaceRoot}/src/PROJECTNAME/bin/Debug/netcoreapp1.1/PROJECTNAME.dll",
            "args": ["--server.urls=http://localhost:50000"],
            "cwd": "${workspaceRoot}/src/PROJECTNAME",
            "stopAtEntry": false,
            "env": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            },
            "sourceFileMap": {
                "/Views": "${workspaceRoot}/Views"
            }
        }
    ]
}

Logs

Crash report:

...

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000000000102031c
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

...

Thread 16 Crashed:
0   libsystem_malloc.dylib        	0x00007fffac11027e malloc_zone_malloc + 103
1   libvsbaseservices.dylib       	0x00000001041c23f8 HeapAlloc + 40
2   libvsdebugeng.impl.dylib      	0x000000010450f11e MakeStream(unsigned char const*, unsigned int, IStream**) + 46
3   libvsdebugeng.impl.dylib      	0x00000001044e6fc8 SymProvider::CDiaLoader::LoadSymbolsForModuleInstance(Microsoft::VisualStudio::Debugger::DkmModuleInstance*) + 312
4   libvsdebugeng.dylib           	0x00000001046b6cc2 dispatcher::DkmModuleInstance::FireCreateEvent() + 274
5   libvsdebugeng.dylib           	0x00000001046b6acd 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           	0x00000001046b7175 ProcAEA58B7861C86E08A55546A1C4D0ACAD + 229
7   libvsdebugeng.impl.dylib      	0x000000010447812c 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      	0x0000000104478d4d ManagedDM::CDbiCallback::DoLoadModule(ICorDebugAppDomain*, ICorDebugModule*, Microsoft::VisualStudio::Debugger::DkmModuleFlags, Microsoft::VisualStudio::Debugger::Clr::DkmClrModuleInstance**) + 253
9   libvsdebugeng.impl.dylib      	0x000000010447cca3 ManagedDM::CDbiCallback::DoDebugEvents(ATL::CAtlList<CComObjectPtr<ManagedDM::CManagedDebugEvent>, ATL::CElementTraits<CComObjectPtr<ManagedDM::CManagedDebugEvent> > >*) + 1603
10  libvsdebugeng.impl.dylib      	0x00000001044b3dc4 ManagedDM::CV2DbiCallback::OnDebugEvent() + 196
11  libvsdebugeng.impl.dylib      	0x0000000104474ddd ManagedDM::CDbiCallback::LoadModule(ICorDebugAppDomain*, ICorDebugModule*) + 541
12  libvsdebugeng.impl.dylib      	0x00000001044b1910 ManagedDM::CV2DbiCallback::LoadModule(ICorDebugAppDomain*, ICorDebugModule*) + 96
13  libmscordbi.dylib             	0x0000000104e48113 ShimProxyCallback::LoadModule(ICorDebugAppDomain*, ICorDebugModule*)::LoadModuleEvent::Dispatch(ManagedEvent::DispatchArgs) + 35
14  libmscordbi.dylib             	0x0000000104e7ea7f CordbProcess::DispatchRCEvent() + 399
15  libmscordbi.dylib             	0x0000000104e880c8 CordbRCEventThread::FlushQueuedEvents(CordbProcess*) + 152
16  libmscordbi.dylib             	0x0000000104e88892 CordbRCEventThread::ThreadProc() + 1074
17  libmscordbi.dylib             	0x0000000104e88a39 CordbRCEventThread::ThreadProc(void*) + 9
18  libmscordaccore.dylib         	0x00000001051f5bf8 CorUnix::CPalThread::ThreadEntry(void*) + 328
19  libsystem_pthread.dylib       	0x00007fffac1a79af _pthread_body + 180
20  libsystem_pthread.dylib       	0x00007fffac1a78fb _pthread_start + 286
21  libsystem_pthread.dylib       	0x00007fffac1a7101 thread_start + 13

I'll be happy to provide more debugging info.

@gregg-miskelly
Copy link
Contributor

@guidobouman There is now a beta release, v1.10.0-beta4, which is available with this fix. See here for instructions on installing.

@gregg-miskelly
Copy link
Contributor

This is a duplicate of #1456

@guidobouman
Copy link
Author

guidobouman commented May 23, 2017

I was sure I tried this beta. But I might have run into another issue before downgrading back to the official release. Let me try this again.

@guidobouman
Copy link
Author

guidobouman commented May 23, 2017

@gregg-miskelly Thanks for getting back so quickly, this was indeed the fix for this issue! (I was having another unrelated issue that I solved later on after reverting back to the official release.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants