It just happens during precompilation I think. I'll look into it and see if
I can get some more information.
On 4 August 2016 at 11:30, Tony Kelman wrote:
> Maybe. What are you running that hits a double free? Does it happen when
> run in julia-debug? What about under gdb?
>
>
Maybe. What are you running that hits a double free? Does it happen when
run in julia-debug? What about under gdb?
On Thursday, August 4, 2016 at 2:16:58 AM UTC-7, Bill Hart wrote:
>
> Ok, I'll hold off making a ticket then. Tony, do you think the double free
> and corruption with Julia 0.5.0
Ok, I'll hold off making a ticket then. Tony, do you think the double free
and corruption with Julia 0.5.0 could be independent of Microsoft. I'm not
seeing that behaviour anywhere else. Do we have any tools that might help
track it down? Or is it just not worth it for now?
Bill.
On 4 August
I don't think there's anything specific we can fix here, we have to wait
for Microsoft to gradually fix the rest of the syscalls they haven't
implemented all the way yet. Good to know this is available without having
to opt in to the unstable test builds of Windows 10 now. Last I looked at
it,
I agree, it would be great to get it going.
I'll open a ticket later on tonight or tomorrow. I'm not sure I can
contribute much more to it myself. I think the first thing to do might be
to contact the libuv people and ask them whether libuv is expected to run
on WSL. It may just be a waiting
Would be great to get this working. Maybe open an issue to track this?
On Wednesday, August 3, 2016, 'Bill Hart' via julia-users <
julia-users@googlegroups.com> wrote:
> In fact, both the old and new versions of libuv seem to fail their test
> suites on WSL. I imagine they tie into the system
I got the Windows 10 anniversary update and turned on the new Windows
subsystem for Linux.
The Julia binaries from the website load, but unfortunately don't fully
work. I had hoped Julia might just work as I had heard many large programs
just work, but alas, not yet.
I tried both 0.4.6 and