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

[ocaml5-issue] Segfault in Lin Out_channel test in 32-bit and bytecode mode #412

Closed
jmid opened this issue Nov 12, 2023 · 1 comment
Closed
Labels
duplicate This issue or pull request already exists ocaml5-issue A potential issue in the OCaml5 compiler/runtime

Comments

@jmid
Copy link
Collaborator

jmid commented Nov 12, 2023

On #411 we saw a segfault in Lin Out_channel test with Domain in a 32-bit trunk/5.2 run:
https://github.com/ocaml-multicore/multicoretests/actions/runs/6826699760/job/18567181221?pr=411

random seed: 125264582
generated error fail pass / total     time test name

[ ]    0    0    0    0 / 1000     0.0s Lin In_channel test with Domain
[ ]    0    0    0    0 / 1000     0.0s Lin In_channel test with Domain (generating)
[✓]    4    0    1    3 / 1000    12.8s Lin In_channel test with Domain

File "src/io/dune", line 21, characters 7-23:
21 |  (name lin_tests_domain)
            ^^^^^^^^^^^^^^^^
(cd _build/default/src/io && ./lin_tests_domain.exe --verbose)
Command got signal SEGV.
[ ]    0    0    0    0 / 5000     0.0s Lin Out_channel test with Domain
@jmid jmid added the ocaml5-issue A potential issue in the OCaml5 compiler/runtime label Nov 12, 2023
@jmid jmid changed the title [ocaml5-issue] Segfault in Lin Out_channel test in 32-bit mode [ocaml5-issue] Segfault in Lin Out_channel test in 32-bit and bytecode mode Dec 11, 2023
@jmid jmid added the duplicate This issue or pull request already exists label Jun 6, 2024
@jmid
Copy link
Collaborator Author

jmid commented Jun 6, 2024

Note: this was first observed shortly after the merge of the compaction PR (Nov 6) which has been established as the cause of #446.

The condition (32bit) and symptoms (crash) are the same. As such I'm closing it as a duplicate.

@jmid jmid closed this as completed Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists ocaml5-issue A potential issue in the OCaml5 compiler/runtime
Projects
None yet
Development

No branches or pull requests

1 participant