-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
@threadcall fragility #17819
Comments
The printing is not threadsafe and there are issues open. This should perhaps be mentioned clearly in the docs for 0.5, if not already there. I wonder if we should test for the presence of print statements in a threads macro and alert the user - or else we will have a flood of these reports. |
|
threadcall was never documented (not in the manual anyway) |
OK. Will document the restriction and fix the bug. |
A fragility following from the fact that it can't call back into Julia:
|
Fixes #17819. Also document not being allowed to call back into Julia.
Fixes #17819. Also document not being allowed to call back into Julia.
Fixes #17819. Also document not being allowed to call back into Julia.
Fixes #17819. Also document not being allowed to call back into Julia.
Fixes JuliaLang#17819. Also document not being allowed to call back into Julia.
Fixes JuliaLang#17819. Also document not being allowed to call back into Julia.
There's multiple issues with
@threadcall
I've spotted while debugging a test.Probably by design, but the docs don't mention such a restriction.
The reason is a missing
ptr
adjustment when creating the args array indo_threadcall
:When debugging 2) by adding some print statements to
do_threadcall
, Julia easily locked up. Not sure whether or not this is expected, but I thought I'd mention it anyway.Tested on latest master.
The text was updated successfully, but these errors were encountered: