XUnitLogChecker: Frames are sometimes unresolved #94721

Activity

1. carlossanlop

   added

   area-Infrastructure-coreclrOnly use for closed issuesOnly use for closed issues

   on Nov 14, 2023
3. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Nov 14, 2023
4. carlossanlop commented on Nov 14, 2023

   

   carlossanlop

   on Nov 14, 2023

   ContributorAuthor

   More actions

   Another example: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-93906-merge-73d789b084234d60b0/System.IO.Compression.Brotli.Tests/1/console.68d2b2ea.log?helixlogtype=result

   Thread Id: 0x1e
         Child SP               IP Call Site
    0xffa24af9d810 0xffa24a9e22ec libclrjit.so!?? at ??:0:0
    0xffa24af9d890 0xffa24a9d0408 libclrjit.so!?? at ??:0:0
    0xffa24af9d8e0 0xffa24a9d6874 libclrjit.so!?? at ??:0:0
    0xffa24af9d990 0xffa24a9d5430 libclrjit.so!?? at ??:0:0
    0xffa24af9da70 0xffa24a9d7f64 libclrjit.so!?? at ??:0:0
    0xffa24af9e0c0 0xffa24a9e1910 libclrjit.so!?? at ??:0:0
    0xffa24af9e180 0xffe3222f56e0 libcoreclr.so!?? at ??:0:0
    0xffa24af9e1f0 0xffe3222f586c libcoreclr.so!?? at ??:0:0
    0xffa24af9e260 0xffe3222f67a0 libcoreclr.so!?? at ??:0:0
    0xffa24af9eef0 0xffe3223453c8 libcoreclr.so!?? at ??:0:0
    0xffa24af9eff0 0xffe322344bf8 libcoreclr.so!?? at ??:0:0
    0xffa24af9f120 0xffe322344220 libcoreclr.so!?? at ??:0:0
    0xffa24af9f1f0 0xffe3223438c0 libcoreclr.so!?? at ??:0:0
    0xffa24af9f2c0 0xffe322387814 libcoreclr.so!?? at ??:0:0
    0xffa24af9f3e0 0xffe322386a28 libcoreclr.so!?? at ??:0:0
    0xffa24af9f500 0xffe322385dc0 libcoreclr.so!?? at ??:0:0
    0xffa24af9f580 0xffe322385bf8 libcoreclr.so!?? at ??:0:0
    0xffa24af9f5c0 0xffe322380ac0 libcoreclr.so!?? at ??:0:0
    0xffa24af9f740 0xffe322381040 libcoreclr.so!?? at ??:0:0
    0xffa24af9f770 0xffe322385b40 libcoreclr.so!?? at ??:0:0
    0xffa24af9f7b0 0xffe3227ff58c libcoreclr.so!?? at ??:0:0
    0xffa24af9f860 0xffe322c93ce0 ld-musl-aarch64.so.1!
   ----------------------------------
   
5. hoyosjs commented on Nov 15, 2023

   

   hoyosjs

   on Nov 15, 2023

   Member

   More actions

   This looks like lack of symbols on the test machine (for some of these) and then missing function table data in the dump (this is a known issue and the only workaround is to modify the registry).
6. JulieLeeMSFT

   assigned

   hoyosjs

   on Jan 17, 2024
7. JulieLeeMSFT

   added this to the 9.0.0 milestone on Jan 17, 2024
8. ghost removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jan 17, 2024
9. JulieLeeMSFT commented on Jan 17, 2024

   

   JulieLeeMSFT

   on Jan 17, 2024

   Member

   More actions

   If it is a missing symbol, we need to find out why it is missing.
10. hoyosjs commented on Jan 25, 2024

    

    hoyosjs

    on Jan 25, 2024

    Member

    More actions

    @carlossanlop

    I haven't yet found newer examples on linux, but for windows there's two issues.

    • Nothing installs sos so you'll never get managed stacks. See how runtime tests do it:

      runtime/src/tests/Common/helixpublishwitharcade.proj

      Lines 783 to 787 in 777f9d9

      	<HelixCorrelationPayload Condition="'$(TestWrapperTargetsWindows)' == 'true'" Include="dotnet-sos">
      	<Destination>sos</Destination>
      	<Uri>https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/flat2/dotnet-sos/$(DotnetSosVersion)/dotnet-sos.$(DotnetSosVersion).nupkg</Uri>
      	</HelixCorrelationPayload>

      and then the call to dotnet sos install as part of the workitems command.
    • Nothing sets a symbol path. You need to set _NT_SYMBOL_PATH to point to the folder that has runtime symbols. Like this (with the correct payload path):

    set "_NT_SYMBOL_PATH=E:\Temp\libs-crash\correlation-payload;E:\Temp\libs-crash\correlation-payload\shared\Microsoft.NETCore.App\9.0.0"
11. JulieLeeMSFT

    assigned

    carlossanlop

    and unassigned

    hoyosjs

    on Jan 31, 2024
12. JulieLeeMSFT commented on Jan 31, 2024

    

    JulieLeeMSFT

    on Jan 31, 2024

    Member

    More actions

    Reassigning to @carlossanlop.
13. ericstj commented on Jan 31, 2024

    

    ericstj

    on Jan 31, 2024

    Member

    More actions

    Looks like we missed some additional setup steps required for the xunit symbolizer tool. @hoyosjs is there anything to audit here to make sure we copied all the relevant steps from the runtime test deployment into libs?
14. ghost added

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Feb 14, 2024
15. carlossanlop

    closed this as completedin #98397on Feb 27, 2024
16. ghost removed

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Feb 27, 2024
17. github-actions

    locked and limited conversation to collaborators on Mar 28, 2024