Skip to content

Disable catch_signals in sc_init#102

Merged
benegee merged 1 commit intomainfrom
bg/change-sc-init-flag
Dec 10, 2025
Merged

Disable catch_signals in sc_init#102
benegee merged 1 commit intomainfrom
bg/change-sc-init-flag

Conversation

@benegee
Copy link
Collaborator

@benegee benegee commented Dec 9, 2025

As found in #35, it might help with current CI failures.

Copy link
Contributor

@spenke91 spenke91 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@benegee
Copy link
Collaborator Author

benegee commented Dec 10, 2025

@spenke91 and I noticed that running with a single thread explicitly avoids the current segmentation fault issues in CI.
We did this via environment variables, see

JULIA_NUM_THREADS: 1
, and via command line for a newly spawned julia process, see
run(`$(Base.julia_cmd()) --threads=1 --check-bounds=yes --project=$(dirname(@__DIR__)) $(abspath("test_all.jl"))`)
.

I still do not understand why this changes anything. At least I verified locally that nthreads and ngcthreads return 1 each, regardless of the threads setting.

Anyway, this suggests #35 could be helpful here. According to https://github.com/cburstedde/libsc/blob/f83ea609a019178af2742f11e1a300c8ee78e9d7/src/sc.h#L813, it disables catching of SIGINT and SIGSEGV.

@benegee benegee merged commit 92f889d into main Dec 10, 2025
63 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants