Hi Erik,
> On 29 Jul 2015, at 3:35 , Erik Schnetter wrote:
> I was able to build openmpi-v2.x-dev-96-g918650a without problems on Edison,
> and also on other systems.
And does it also work as expected after you have build it? :-)
Thanks
Mark
Hello,
On 07/28/15 17:34, Schlottke-Lakemper, Michael wrote:
That’s what I suspected. Thank you for your confirmation.
you are mistaken, the allocation is 51 bytes long, i.e. valid bytes are at
offsets 0 to 50. But since the read of 4 bytes starts at offset 48, the bytes at
offsets 48, 49, 5
Thomas,
can you please elaborate ?
I checked the code of opal_os_dirpath_create and could not find where such
a thing can happen
Thanks,
Gilles
On Wednesday, July 29, 2015, Thomas Jahns wrote:
> Hello,
>
> On 07/28/15 17:34, Schlottke-Lakemper, Michael wrote:
>
>> That’s what I suspected. Tha
On Tue, Jul 28, 2015 at 11:52 PM, Mark Santcroos wrote:
> Hi Erik,
>
> > On 29 Jul 2015, at 3:35 , Erik Schnetter wrote:
> > I was able to build openmpi-v2.x-dev-96-g918650a without problems on
> Edison, and also on other systems.
>
> And does it also work as expected after you have build it? :-
If it is helpful, I can try to compile OpenMPI with debug information and get
more details on the reported error. However, it would be good if someone could
tell me the necessary compile flags (on top of -O0 -g) and it would take me
probably 1-2 weeks to do it.
Michael
Original messa
If you have the time, it would be helpful. You might also configure
—enable-debug.
Meantime, I can take another gander to see how it could happen - looking at the
code, it sure seems impossible, but maybe there is some strange path that would
break it.
> On Jul 29, 2015, at 6:29 AM, Schlottke
