On 2 February 2016 at 11:07, Gilles Gouaillardet wrote:
> Lisandro,
>
> here is attached a patch (master does things differently, so this has to be
> a one-off patch anyway)
> could you please give it a try ?
>
OK, just tried your patch: the warnings went away, valgrind didn't complain.
> btw,
Lisandro,
here is attached a patch (master does things differently, so this has to
be a one-off patch anyway)
could you please give it a try ?
btw, how do you get these warnings automatically ?
Cheers,
Gilles
On 2/2/2016 12:02 AM, Lisandro Dalcin wrote:
You might argue that the attached te
You might argue that the attached tests are naive, but still... (Open
MPI v1.10.2)
$ mpicc win_post_wait.c
$ mpiexec -n 1 ./a.out
malloc debug: Request for 0 bytes (osc_pt2pt_active_target.c, 76)
malloc debug: Request for 0 bytes (osc_pt2pt_active_target.c, 78)
$ mpiexec -n 2 ./a.out
malloc debug:
On 27 August 2014 02:38, Jeff Squyres (jsquyres) wrote:
> If you have reproducers, yes, that would be most helpful -- thanks.
>
Here you have another one...
$ cat igatherv.c
#include
int main(int argc, char *argv[])
{
signed char a=1,b=2;
int rcounts[1] = {0};
int rdispls[1] = {0};
MPI_
On 27 August 2014 02:38, Jeff Squyres (jsquyres) wrote:
> If you have reproducers, yes, that would be most helpful -- thanks.
>
OK, here you have something to start. To be fair, this is a reduction
with zero count. I have many other tests for reductions with zero
count that are failing.
Does Ope
If you have reproducers, yes, that would be most helpful -- thanks.
On Aug 26, 2014, at 12:26 PM, Lisandro Dalcin wrote:
> I'm getting a bunch of the following messages. Are they signaling some
> easy-to-fix internal issue? Do you need code to reproduce each one?
>
> malloc debug: Request for 0
I'm getting a bunch of the following messages. Are they signaling some
easy-to-fix internal issue? Do you need code to reproduce each one?
malloc debug: Request for 0 bytes (coll_libnbc_ireduce_scatter_block.c, 67)
...
malloc debug: Request for 0 bytes (nbc_internal.h, 496)
...
malloc debug: Reque
I'll look into it in the next couple of days.
Thanks
Edgar
George Bosilca wrote:
> This is an artifact of using the gatherv (or the scatterv) on an
> inter-communicator without any useful data (i.e. either count of zero or
> empty datatypes). Looks more like a synchronization than a real operati
This is an artifact of using the gatherv (or the scatterv) on an
inter-communicator without any useful data (i.e. either count of zero or empty
datatypes). Looks more like a synchronization than a real operation.
george.
On May 5, 2010, at 20:17 , Lisandro Dalcin wrote:
> After building 1.4
Thanks for the report -- I've filed
https://svn.open-mpi.org/trac/ompi/ticket/2405.
On May 5, 2010, at 8:17 PM, Lisandro Dalcin wrote:
> After building 1.4.2 with debug flags to configure, I get this (I've
> got these warnings in previous releases, too):
>
> malloc debug: Request for 0 bytes (c
After building 1.4.2 with debug flags to configure, I get this (I've
got these warnings in previous releases, too):
malloc debug: Request for 0 bytes (coll_inter_gatherv.c, 94)
malloc debug: Request for 0 bytes (coll_inter_gatherv.c, 94)
malloc debug: Request for 0 bytes (coll_inter_gatherv.c, 94)
11 matches
Mail list logo
