Greetings, and thanks for trying out our Java bindings. Can you provide some more details? E.g., is there a particular program you're running that incurs these problems? Or is there even a particular MPI function that you're using that results in this segv (e.g., perhaps we have a specific bug somewhere)?
Can you reduce the segv to a small example that we can reproduce (and therefore fix)? On Mar 10, 2014, at 12:05 AM, Saliya Ekanayake <esal...@gmail.com> wrote: > Hi, > > I have 8 nodes each with 2 quad core sockets. Also, the nodes have IB > connectivity. I am trying to run OMPI Java binding in OMPI trunk revision > 30301 with 8 procs per node totaling 64 procs. This gives a SIGSEV error as > below. > > I wonder if you have any suggestion to resolve this? > > Thank you, > Saliya > > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x000000313867b75b, pid=12229, tid=47864973515072 > # > # JRE version: Java(TM) SE Runtime Environment (8.0-b118) (build > 1.8.0-ea-b118) > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b60 mixed mode linux-amd64 > compressed oops) > # Problematic frame: > # C [libc.so.6+0x7b75b] memcpy+0x15b > > > -- > Saliya Ekanayake esal...@gmail.com > http://saliya.org > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
