You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure about the specifics, but I'm filing this issue as a placeholder.
When I made the change in #299 to process unmerged ETL files, this changed the behavior of some of @vvuk's CoreCLR integration code. Specifically, the names we get when we read the unmerged ETL file are different from the names we expect.
For example, for Microsoft-Windows-DotNETRuntimeRundown/CLRMethodRundown/MethodDCStartVerbose, we currently instead get the name Microsoft-Windows-DotNETRuntimeRundown/Method /DCStartVerbose (including the space) from the unmerged ETL.
As a workaround, one could create merged ETL file manually and feed it into samply import.
Vlad had some ideas for what might be needed to fix this, but I forgot the specifics. If someone wants to dig into this, I can try to find his message in the https://chat.mozilla.org/#/room/#profiler:mozilla.org backscroll.
The text was updated successfully, but these errors were encountered:
I'm not sure about the specifics, but I'm filing this issue as a placeholder.
When I made the change in #299 to process unmerged ETL files, this changed the behavior of some of @vvuk's CoreCLR integration code. Specifically, the names we get when we read the unmerged ETL file are different from the names we expect.
For example, for
Microsoft-Windows-DotNETRuntimeRundown/CLRMethodRundown/MethodDCStartVerbose
, we currently instead get the nameMicrosoft-Windows-DotNETRuntimeRundown/Method /DCStartVerbose
(including the space) from the unmerged ETL.As a workaround, one could create merged ETL file manually and feed it into
samply import
.Vlad had some ideas for what might be needed to fix this, but I forgot the specifics. If someone wants to dig into this, I can try to find his message in the https://chat.mozilla.org/#/room/#profiler:mozilla.org backscroll.
The text was updated successfully, but these errors were encountered: