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 grea
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
>
Here are the two files I tried - not from the same machine. The foo.xml works,
the topo.xml segfaults
topo.xml
Description: XML document
foo.xml
Description: XML document
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
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, Ral
I didn't try loading it with lstopo - just tried the OMPI trunk. It loads okay,
but segfaults when you try to find an object by depth
#0 0x0001005fe5dc in opal_hwloc172_hwloc_get_obj_by_depth (topology=Cannot
access memory at address 0xfff7
) at traversal.c:623
#1 0x000100b
Try adding HWLOC_DEBUG_CHECK=1 in your environment, it will enable many
assertions at the end of hwloc_topology_load()
Brice
Le 21/09/2013 01:03, Ralph Castain a écrit :
> I didn't try loading it with lstopo - just tried the OMPI trunk. It
> loads okay, but segfaults when you try to find an obj
Hmmm...nope, not a peep (no extra output at all). Just segfaulted like before.
On Sep 20, 2013, at 4:06 PM, Brice Goglin wrote:
> Try adding HWLOC_DEBUG_CHECK=1 in your environment, it will enable many
> assertions at the end of hwloc_topology_load()
>
> Brice
>
>
>
> Le 21/09/2013 01:03, R
Strange, the backtrace below looks total crazy, I don't see how debug
checks could still pass in that case.
Any chance you valgrind that thing?
Brice
Le 21/09/2013 01:09, Ralph Castain a écrit :
> Hmmm...nope, not a peep (no extra output at all). Just segfaulted like
> before.
>
> On Sep 20, 20
Okay, I found it - was a sequencing problem in OMPI itself (we "set" the new
topology too late in the setup sequence). Sorry for false alarm.
Thanks for the help!
Ralph
On Sep 20, 2013, at 11:36 PM, Brice Goglin wrote:
> Strange, the backtrace below looks total crazy, I don't see how debug che
