mscordbi!Cordb::SetTargetCLR
mscordbi!CoreCLRCreateCordbObjectEx
mscordbi!CoreCLRCreateCordbObject dbgshim!CreateCoreDbgWithoutSandboxSupport
dbgshim!CreateCoreDbg dbgshim!RuntimeStartupHelper::InvokeStartupCallback
dbgshim!RuntimeStartupHandler
dbgshim!InvokeStartupCallback dbgshim!StartupHelperThread
This issue is tracking the work necessary to support single-file diagnostics. Our goal is to deliver parity with debugging and profiling with framework dependent applications where applicable.
dbgshimneeds an ELF parser to identify if a module is CoreCLR + extract the DAC/DBI keys. There's currently a copy in use in the runtime forcreatedumpand the DAC on Linux dumps and one used in SOS forOpenVirtualProcess.dbgshimOVP needs updatedILibraryProvidercallback interface that accepts buildid information for DAC/DBI. This receives the DAC/DBI keys that were retrieved.dbgshimlive debugging case needs to integrateILibraryProviderso that the caller can locate DAC/DBI instead ofdbgshim.runtime/src/coreclr/src/pal/src/thread/process.cpp
Line 1654 in 6438d08
createdumpand a portion of the DAC need to be linked into the hostcreatedumpneeds to be modified to use a linked in DAC rather than searching for it.