Hi OpenMPI
I am trying to create a Java GUI to control and run an MPI application. I
can run an MPI process from my command line, but am unable to run via the
Java Process Builder.
I get the following error immediately after the process starts:
[SCI053_VM003:02928] ..\..\openmpi-1.6.4\opal\event
On 07/23/2013 02:22 PM, Ralph Castain wrote:
> Yeah, it's failing when trying to unpack the topology obtained from
> hwloc. My guess is that one of the following calls changed in
> hwloc-1.4.3:
>
It appears to be this one.
hwloc_topology_set_xmlbuffer
I'll return what I've gathered so far to th
On Jul 23, 2013, at 12:10 PM, Andre Dozier wrote:
> I was using the OMPI trunk version 1.9a1r28764...
>
> I tried building openmpi both with and without GC_DOES_PINNING defined,
> because I noticed that the MPI calls are handled differently with that
> defined (although I may not have defined
I was using the OMPI trunk version 1.9a1r28764...
I tried building openmpi both with and without GC_DOES_PINNING defined,
because I noticed that the MPI calls are handled differently with that
defined (although I may not have defined it in the correct place
ompi/mpi/java/c/mpiJava.h). With
That's understandable - if you don't disable xml2, then hwloc uses the xml2
library to do the topology encoding. We rely on their internal "quasi-xml"
encoding method, which I believe provides some different data (and definitely
different format). I suspect this is causing the confusion, though
On 07/23/2013 02:22 PM, Ralph Castain wrote:
> Yeah, it's failing when trying to unpack the topology obtained from hwloc.
What I find very interesting is that the hwloc configure options
--disable-cairo --disable-libxml2 turn the bug off.
I'll keep walking through the execution in gdb maybe I'll
I suspect it has fallen stale as the Java bindings are being reworked as we
speak. I hope to see them committed back to the trunk shortly.
On Jul 20, 2013, at 10:01 PM, Saliya Ekanayake wrote:
> Hi,
>
> I obtained the nightly build openmpi-1.9a1r28881 (on 7/19/13) and built it
> with java en
There shouldn't be an inter-language issue here as all the Java code does is
use a JNI module to access the C bindings. Were you using the Java bindings in
the OMPI trunk? Or were you using a 3rd party library?
On Jul 22, 2013, at 9:13 AM, Andre Dozier wrote:
> I never got mpiJava to stop free
Yeah, it's failing when trying to unpack the topology obtained from hwloc. My
guess is that one of the following calls changed in hwloc-1.4.3:
if (0 != hwloc_topology_set_xmlbuffer(t, xmlbuffer, strlen(xmlbuffer)))
{
rc = OPAL_ERROR;
free(xmlbuffer);
h
On 07/23/2013 09:54 AM, Jeff Squyres (jsquyres) wrote:
>
> I don't know if Fedora RPMs include -g in their builds, or if Fedora
> includes a debuginfo RPM that you could install such that you can attach
> a debugger and be able to dig into OMPI's internals yourself.
>
There is a debuginfo packag
On 07/23/2013 06:56 AM, Jeff Squyres (jsquyres) wrote:
> With this embedded mechanism, we're calling hwloc's configury with
> the moral equivalent of:
>
> ./configure --disable-cairo --disable-libxml2 --enable-xml
> --with-hwloc-symbol-prefix=opal_hwloc152_ --enable-embedded-mode
I configured hwl
Kevin --
I don't know if Fedora RPMs include -g in their builds, or if Fedora includes a
debuginfo RPM that you could install such that you can attach a debugger and be
able to dig into OMPI's internals yourself.
If that doesn't work, you might need to build from source yourself, link
against
On 07/23/2013 09:36 AM, Ralph Castain wrote:
> The Fedora package is built optimized, so no OMPI debugging output is
> available and a debugger won't tell us a lot.
The fedora package comes with a debuginfo package that has everything
gdb needs to let me step through the openmpi functions.
I also
I see - I didn't look at the redhat bug list. Sadly, I have no idea how to
debug it. The Fedora package is built optimized, so no OMPI debugging output is
available and a debugger won't tell us a lot.
Best guess is that there is something in the build that doesn't match the
user's system. The n
On Jul 23, 2013, at 8:54 AM, Ralph Castain wrote:
>> Yes, it's curious that they can't reproduce your issue,
>
> Guess I missed this - where does it say that they can't reproduce the issue??
> I'm suspicious because build-from-source produced a working result.
Orion mentioned it in https://bug
On Jul 23, 2013, at 3:56 AM, Jeff Squyres (jsquyres) wrote:
> On Jul 21, 2013, at 8:50 AM, Kevin H. Hobbs wrote:
>
>>> Ah! That would indicate an issue with the external hwloc
>>> package they provided, which is the big reason we don't
>>> recommend installing from packages.
>>
>> I'll happil
On Jul 21, 2013, at 8:50 AM, Kevin H. Hobbs wrote:
>> Ah! That would indicate an issue with the external hwloc
>> package they provided, which is the big reason we don't
>> recommend installing from packages.
>
> I'll happily report the bug to the hwloc developers.
I don't think that this is ne
17 matches
Mail list logo