The other closest explanation is here -
https://code.google.com/p/chromium/issues/detail?id=31809#c31 . Though, I
still don't know what to fix to get MPI.jl up and running on my system....

On Fri, Jan 9, 2015 at 5:53 PM, Amit Murthy <[email protected]> wrote:

> A google search for that error all showed up issues related to either a)
> cross-compiling or b) memory allocated by one library being
> freed/realloc'ed by another. Issue -
> https://github.com/JuliaParallel/MPI.jl/issues/25
>
> On Fri, Jan 9, 2015 at 3:20 PM, Viral Shah <[email protected]> wrote:
>
>> Oops - realized that you are running in fact in linux. Sorry - ignore my
>> comment then. Could it be a julia issue, or some MPI call that is not being
>> used correctly and is corrupting memory?
>>
>> -viral
>>
>>
>>
>> > On 09-Jan-2015, at 3:18 pm, Viral Shah <[email protected]> wrote:
>> >
>> > How about trying out some other MPI library? Mac support may vary
>> across multiple open source implementations.
>> >
>> > -viral
>> >
>> > On Thursday, January 8, 2015 at 9:28:21 PM UTC+5:30, Amit Murthy wrote:
>> > Hello,
>> >
>> > On a Ubuntu 14.10 system, I am having trouble getting MPI.jl up and
>> running.
>> >
>> > The deps build goes through fine, but fails on running tests with the
>> following error:
>> >
>> > amitm@amitm-macbookpro:~/.julia/v0.4/MPI/test$ mpirun -np 4 julia
>> test_bcast.jl
>> >
>> >
>> > WARNING: deprecated syntax "{a=>b, ...}" at
>> /home/amitm/.julia/v0.4/MPI/src/mpi-base.jl:19.
>> > Use "Dict{Any,Any}(a=>b, ...)" instead.
>> >
>> >
>> > .....
>> > Inconsistency detected by ld.so: dl-minimal.c: 136: realloc: Assertion
>> `ptr == alloc_last_block' failed!
>> >
>> > ....
>> >
>> >
>> >
>> >
>> > systeminfo:
>> >
>> >   | | |_| | | | (_| |  |  Version 0.4.0-dev+2558 (2015-01-08 07:21 UTC)
>> >  _/ |\__'_|_|_|\__'_|  |  Commit 2bb647a (0 days old master)
>> > |__/                   |  x86_64-linux-gnu
>> >
>> >
>> > It is actually a MacbookPro running Ubuntu.
>> >
>> >
>> > FWIW, it works fine on a different Ubuntu 14.04 Core i5 system.
>> >
>> >   Amit
>> >
>>
>>
>

Reply via email to