-
Notifications
You must be signed in to change notification settings - Fork 209
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
Exception output from many threads is not helpful #1780
Comments
I don't see a segfault here, just the expected exception reporting. |
The segfault happened if you replace the |
In that case you just get a lot of output on your terminal. I assume you hit CTRL-C, which might have killed Julia or CUDA then. In any case, there isn't much we can do about this, as I/O is currently handled by CUDA. Maybe we could limit output by keeping track of written bytes and capping it, but that doesn't sound very satisfying. |
I didn't hit CTRL-C but wait for the output stop. It still result in segfault. Another issue is that this error is not always captured. On the machine (I reported above) the error is not shown unless I start julia with |
mapreduce
kernel cause segmentation fault
That's intentional. If you run without
|
Oh, I thought it would give a compile error, but it seems to run successfully and generate the correct result on that machine. |
We can't generate a compile error because of Julia's dynamic semantics. You should still see a run-time exception though, albeit without a stack trace (you need |
It didn't get any exception on that machine. And on another machine, it randomly failed. |
Describe the bug
This would crash julia if the array is large, happened on both 1.8.5 and 1.9-beta4.
To reproduce
The Minimal Working Example (MWE) for this bug:
Manifest.toml
Version info
Details on Julia:
Details on CUDA:
The text was updated successfully, but these errors were encountered: