I can't see any segfault. Where does the segfault occurs for you? In OMPI only (or lstopo too)? When loading or when using the topology?

I tried lstopo on that file with and without HWLOC_NO_LIBXML_IMPORT=1 (in case the bug is in one of XML backends), looks ok.

Brice





Le 20/09/2013 23:53, Ralph Castain a écrit :
Here are the two files I tried - not from the same machine. The foo.xml works, the topo.xml segfaults





One of our users reported it from their machine, but I don't have their topo file.

On Sep 20, 2013, at 2:41 PM, Brice Goglin <Brice.Goglin@inria.fr> wrote:

Hello,
I don't see anything reason for such an incompatibility. But there are
many combinations, we can't test everything.
I can't reproduce that on my machines. Can you send the XML output of
both versions on one of your machines?
Brice



Le 20/09/2013 23:32, Ralph Castain a écrit :
Hi folks

I've run across a rather strange behavior. We have two branches in OMPI - the devel trunk (using hwloc v1.7.2) and our feature release series (using hwloc 1.5.2). I have found the following:

*the feature series can correctly load an xml file generated by lstopo of versions 1.5 or greater

* the devel series can correctly load an xml file generated by lstopo of versions 1.7 or greater, but not files generated by prior versions. In the latter case, I segfault as soon as I try to use the loaded topology.

Any ideas why the discrepancy? Can I at least detect the version used to create a file when loading it so I can error out instead of segfaulting?

Ralph

_______________________________________________
hwloc-devel mailing list
hwloc-devel@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
_______________________________________________
hwloc-devel mailing list
hwloc-devel@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel

      

_______________________________________________
hwloc-devel mailing list
hwloc-devel@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel