Description
EventPipe events like ModuleDCStop, DomainModuleDCStop, KnownPathProbed, ResolutionAttempted, KnownPathProbed, AssemblyLoaderStop mixes relative and absolute paths for assemblies in fileds like ModuleILPath, FilePath, ResultAssemblyPath etc. On OSX these paths tend to always be absolute. CoreCLR on Android should either use relative or absolute paths for these fields.
Data was primarily collected on Android sample HelloWorld in dotnet/runtime repro. In this scenario host extract all assemblies out of APK into internal file system on before running app, so this issue might be related to the host and/or how these paths are resolved when emitting the events. Once figured out on the sample, we should also verify that we get expected behavior when running together with dotnet Android SDK, since they use different solutions depending on how the app gets build. It also utilizes customization to assembly loader that would need to be validated together with above EventPipe events.
Metadata
Metadata
Assignees
Type
Projects
Status