-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
segfault in libcoreclr.so`CallDescrWorkerWithHandler #66970
Comments
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue Detailshttps://dev.azure.com/dnceng/public/_build?definitionId=690&_a=summary
cc: @dotnet/ncl
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue Detailshttps://dev.azure.com/dnceng/public/_build?definitionId=690&_a=summary
cc: @dotnet/ncl
|
Tagging subscribers to this area: @dotnet/ncl Issue Detailshttps://dev.azure.com/dnceng/public/_build?definitionId=690&_a=summary
cc: @dotnet/ncl
|
Why did you change the label @agocke ? I feel this got broken by changes outside of HTTP and HTTP itself is not culprit. |
Since this is specific to those tests, it's likely it will need product expertise in those areas to investigate, as opposed to the broader runtime. If this is specific to coreeng infra, then runtime doesn't seem like the right place for this issue. |
This looks like regression from #65738 basically when the coreclr starts it fails with SIGSEGCV
The steps are tedious but it is easy to reproduce once the containers are all built. I don't know if the main trigger is https://github.com/dotnet/runtime/blob/main/eng/pipelines/libraries/enterprise/linux.yml Please let me know @janvorli if you have any thoughts or if I can help anyhow with the investigation. |
@wfurt can you please disassemble the code at 0x00007fff7c81ea08? |
Seems like compiler bug. The container had old llvm 3.9. When we rebuild with llvm-10 the crash is gone. |
https://dev.azure.com/dnceng/public/_build?definitionId=690&_a=summary
Seems to start failing consistently around end of last week
There is not much info but the xunit even did not start.
Unfortunately this seems to run only on selected PRs so there is no good tracking when it start failing.
I feel we should add periodic runs and guard agains infrastructure changes.
cc: @dotnet/ncl
The text was updated successfully, but these errors were encountered: