When you suspect @inbounds, the much easier approach is to start julia with
julia --check-bounds=yes
and it will ignore all @inbounds statements. This even affects base julia
itself, and is therefore both easier and more thorough.
If you identify a BoundsError triggered by one of julia's functions (rather
than one of your own), please do report it as a bug.
Best,
--Tim
On Sunday, April 10, 2016 04:25:48 PM K leo wrote:
> These couple weeks I ran julia (0.4.5) on a Xubuntu guest of VirtualBox
> hosted by a Macbook Pro. During the hour-long runs, the system crashed a
> few times: user interface froze. This has happened a few times in the past
> when I ran Julia natively on a Xubuntu computer. So hardware problem can
> be ruled out.
>
> Trying to guess what could be the problem for the crashes, I put my
> attention on the use of @inbounds and @simd in the code. The documentation
> says @inbounds can cause crash when the index gets out of bound. @simd was
> not said of possibly causing crashes, but it is said of being
> experimental. So I took those out and re-run the code.
>
> After a few hours, the code finishes without crashing. Though this does
> not lead to the conclusion that the two modifiers were the culprit, as the
> code did not crash everytime in the past, this rather makes me wonder if
> @inbounds can possibly be the cause. Look, the code finishes without
> having an index out of bound problem. Is this enough to conclude that
> @inbounds was not the problem?
>
> What can make @simd crash the system?
>
> Another possible cause might be the version of Julia I used. For the past
> weeks, I used the Linux generic version of Julia. This successful run was
> on the version I got from Ubuntu's PPA. In the past, I also juggled
> between the two sources for Julia. I can't be certain in saying that the
> generic version crashes on ubuntu, but my question is what are the real
> differences between the two version of Julia?
