We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Due to a change in GNU malloc, Moscow ML may crash on 64 bit architectures as well as on those 32 bit architectures that use glibc 2.7.
Originally reported by HOL developers
The text was updated successfully, but these errors were encountered:
Can be fixed by disabling the use of mmap from malloc.
For example by adding mallopt(M_MMAP_MAX, 0); to `init_gc` in `gc_ctrl.c` before setting the minor heap size.
Sorry, something went wrong.
The above fix with mallopt is of cause just hiding the root cause.
mallopt
It's more likely that the bug is to be found somewhere in the GC. For example, at http://github.com/kfl/mosml/blob/Rel-2.10/src/runtime/memory.c#L45 we assign a negative value to an unsigned value. And at http://github.com/kfl/mosml/blob/Rel-2.10/src/runtime/memory.c#L58 we free memory allocated by alligned_alloc.
free
alligned_alloc
Updated the interface to uses slices, which in turn made the
bfd9c47
implementation easier. Closes bug kfl#3
This issue should now be fixed
kfl
No branches or pull requests
Due to a change in GNU malloc, Moscow ML may crash on 64 bit architectures as well as on those 32 bit architectures that use glibc 2.7.
Originally reported by HOL developers
The text was updated successfully, but these errors were encountered: