Hey Paul -- I'm going to move this over to the hwloc users list; let's see if we can get this issue addresses over there. I already noticed an oddity in the XML file you sent.
On Oct 31, 2013, at 1:28 PM, Paul Kapinos <kapi...@rz.rwth-aachen.de> wrote: > Hello all, > > using 1.7.x (1.7.2 and 1.7.3 tested), we get SIGSEGV from somewhere in-deepth > of 'hwlock' library - see the attached screenshot. > > Because the error is strongly aligned to just one single node, which in turn > is kinda special one (see output of 'lstopo -'), it smells like an error in > the 'hwlock' library. > > Is there a way to disable hwlock or to debug it in somehow way? > (besides to build a debug version of hwlock and OpenMPI) > > Best > > Paul > > > > > > > > -- > Dipl.-Inform. Paul Kapinos - High Performance Computing, > RWTH Aachen University, Center for Computing and Communication > Seffenter Weg 23, D 52074 Aachen (Germany) > Tel: +49 241/80-24915 > <lstopo_linuxitvc00.txt><opal_hwlock_SIGSEGV.png><lstopo_linuxitvc00.xml>_______________________________________________ > 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/
