---
> *From:* devel on behalf of George
> Bosilca via devel
> *Sent:* Wednesday, May 4, 2022 10:20 AM
> *To:* Open MPI Developers
> *Cc:* George Bosilca
> *Subject:* Re: [OMPI devel] Possible Bug / Invalid Read in Ialltoallw
>
> Damien,
>
> As Gilles indica
ay 4, 2022 10:20 AM
To: Open MPI Developers
Cc: George Bosilca
Subject: Re: [OMPI devel] Possible Bug / Invalid Read in Ialltoallw
Damien,
As Gilles indicated an example would be great. Meanwhile, as you already have
access to the root cause with a debugger, can you check what branch of the if
Damien,
As Gilles indicated an example would be great. Meanwhile, as you already
have access to the root cause with a debugger, can you check what branch of
the if regarding the communicator type in the
ompi_coll_base_retain_datatypes_w function is taken. What is the
communicator type ? Intra or
Damian,
Thanks for the report!
could you please trim your program and share it so I can have a look?
Cheers,
Gilles
On Wed, May 4, 2022 at 10:27 PM Damian Marek via devel <
devel@lists.open-mpi.org> wrote:
> Hello,
>
> I have been getting intermittent memory corruptions and segmentation
>
Hello,
I have been getting intermittent memory corruptions and segmentation faults
while using Ialltoallw in OpenMPI v4.0.3. Valgrind also reports an invalid read
in the "ompi_coll_base_retain_datatypes_w" function defined in
"coll_base_util.c".
Running with a debug build of ompi an assertion
