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

Segmentation fault on ARMv7 platforms with .NET 6.0.33 #109739

Open
mreid-tt opened this issue Nov 8, 2024 · 7 comments
Open

Segmentation fault on ARMv7 platforms with .NET 6.0.33 #109739

mreid-tt opened this issue Nov 8, 2024 · 7 comments
Labels
area-VM-coreclr untriaged New issue has not been triaged by the area owner

Comments

@mreid-tt
Copy link

mreid-tt commented Nov 8, 2024

Describe the bug

Segmentation fault reported on ARMv7 platforms for applications with .NET 6.0.33. Specifically, errors like:

Failed to load /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.33/libcoreclr.so, error: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.27' not found (required by /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.33/libcoreclr.so)

or with .NET 6.0.35:

Failed to load /volume1/@apptemp/radarr/radarr_update/libcoreclr.so, error: /lib/libm.so.6: version `GLIBC_2.27' not found (required by /volume1/@apptemp/radarr/radarr_update/libcoreclr.so)

To Reproduce

Existing projects built with SDK 6.0.424 run fine (.NET 6.0.32) but seem to break with SDK 6.0.425 or later (.NET 6.0.33 or later) on ARMv7 platforms.
E.g. dotnet/core#9447 (comment), Radarr/Radarr#10653 and SynoCommunity/spksrc#6309.

Exceptions (if any)

The issue is not reproducible on x86_64 platforms.

Further technical details

  • Include the output of dotnet --info
  • The IDE (VS / VS Code/ VS4Mac) you're running on, and its version
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Nov 8, 2024
@montigab78
Copy link

Same issue on an IoT edge at my company. This is very bad as it happens even if no change has been made on source code.

@marcpopMSFT marcpopMSFT transferred this issue from dotnet/sdk Nov 12, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 12, 2024
Copy link
Contributor

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

@mreid-tt
Copy link
Author

mreid-tt commented Nov 18, 2024

Any update on this? It seems that applications build with anything newer than SDK 6.0.424 has the issue on ARMv7 platforms.

@mreid-tt mreid-tt changed the title Segmentation fault on ARMv7 platforms with .NET 6.0.33 Segmentation fault on ARMv7 platforms with SDK 6.0.424 (.NET 6.0.33) Nov 20, 2024
@mreid-tt mreid-tt changed the title Segmentation fault on ARMv7 platforms with SDK 6.0.424 (.NET 6.0.33) Segmentation fault on ARMv7 platforms with SDK 6.0.425 (.NET 6.0.33) Nov 20, 2024
@mreid-tt
Copy link
Author

@marcpopMSFT I note you transferred this from the dotnet/sdk area but I do believe this is an SDK issue since it happens for applications built with a specific SDK version.

@vcsjones vcsjones removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 20, 2024
@marcpopMSFT
Copy link
Member

When applications themselves crash, it's typically something in the runtime or the runtime install that's the issue as the SDK is no longer running at that point. It could be app construction but less common. Hence why I moved it.

@mreid-tt mreid-tt changed the title Segmentation fault on ARMv7 platforms with SDK 6.0.425 (.NET 6.0.33) Segmentation fault on ARMv7 platforms with .NET 6.0.33 Nov 21, 2024
@mreid-tt
Copy link
Author

Any update on this issue @mangod9?

@montigab78
Copy link

Any update on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-VM-coreclr untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

5 participants