Bug on julia 1.0 ubuntu #28998
Labels
bug
Indicates an unexpected problem or unintended behavior
missing data
Base.missing and related functionality
Comments
|
A comment from LeoK987 on discourse: But, if I first include the file before using Bug, then Julia coredumps: |
|
Amazing ! and at the second pass: everything looks ok ... except the last 6 in the array is replaced by |
|
With the following module (no I get a new kind of so far, so good, until: And of course everything works fine for: or: Baffling ! |
|
Looks like what's happening here is that |
Keno
added a commit
that referenced
this issue
Sep 3, 2018
The array was allocated based on the serialized `elsize` of the array, however, unions get an extra selector array after the regular storage which was not allocated (because we didn't know it was gonna be a union array at the time when we allocated it). According to a48eeef we cannot look at the element type to allocate the array, so we need to serialize a bit to indicate that we will have a union array. Fixes #28998
Keno
added a commit
that referenced
this issue
Sep 3, 2018
The array was allocated based on the serialized `elsize` of the array, however, unions get an extra selector array after the regular storage which was not allocated (because we didn't know it was gonna be a union array at the time when we allocated it). According to a48eeef we cannot look at the element type to allocate the array, so we need to serialize a bit to indicate that we will have a union array. Fixes #28998
Keno
added a commit
that referenced
this issue
Sep 4, 2018
The array was allocated based on the serialized `elsize` of the array, however, unions get an extra selector array after the regular storage which was not allocated (because we didn't know it was gonna be a union array at the time when we allocated it). According to a48eeef we cannot look at the element type to allocate the array, so we need to serialize a bit to indicate that we will have a union array. Fixes #28998
KristofferC
pushed a commit
that referenced
this issue
Sep 4, 2018
The array was allocated based on the serialized `elsize` of the array, however, unions get an extra selector array after the regular storage which was not allocated (because we didn't know it was gonna be a union array at the time when we allocated it). According to a48eeef we cannot look at the element type to allocate the array, so we need to serialize a bit to indicate that we will have a union array. Fixes #28998 (cherry picked from commit e7d7259)
KristofferC
pushed a commit
that referenced
this issue
Sep 8, 2018
The array was allocated based on the serialized `elsize` of the array, however, unions get an extra selector array after the regular storage which was not allocated (because we didn't know it was gonna be a union array at the time when we allocated it). According to a48eeef we cannot look at the element type to allocate the array, so we need to serialize a bit to indicate that we will have a union array. Fixes #28998 (cherry picked from commit e7d7259)
KristofferC
pushed a commit
that referenced
this issue
Sep 8, 2018
The array was allocated based on the serialized `elsize` of the array, however, unions get an extra selector array after the regular storage which was not allocated (because we didn't know it was gonna be a union array at the time when we allocated it). According to a48eeef we cannot look at the element type to allocate the array, so we need to serialize a bit to indicate that we will have a union array. Fixes #28998 (cherry picked from commit e7d7259)
KristofferC
pushed a commit
that referenced
this issue
Feb 11, 2019
The array was allocated based on the serialized `elsize` of the array, however, unions get an extra selector array after the regular storage which was not allocated (because we didn't know it was gonna be a union array at the time when we allocated it). According to a48eeef we cannot look at the element type to allocate the array, so we need to serialize a bit to indicate that we will have a union array. Fixes #28998 (cherry picked from commit e7d7259)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found a bug in my environment
To reproduce it, make a file
Bug.jlwith the following contents:Then start the REPL and type
using Bug. Then typing any command like1+1or just exiting the REPLwith ^D shows the bug which crashs julia. Here is the bug message:
Finally here are my installed packages:
The text was updated successfully, but these errors were encountered: