[OMPI devel] malloc(0) warnings

2010-05-05 Thread Lisandro Dalcin
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)

Re: [OMPI devel] System V Shared Memory forOpenMPI:Request forCommunity Input and Testing

2010-05-05 Thread Samuel K. Gutierrez
On May 5, 2010, at 6:10 AM, Jeff Squyres wrote: On May 4, 2010, at 9:53 AM, Ashley Pittman wrote: Point noted. But actually -- can you give specific reasons as to why a user should care? Keep in mind that this would be a short- lived fork'ed process -- not "spawn" in the MPI sense of the w

Re: [OMPI devel] System V Shared Memory for OpenMPI:Request forCommunity Input and Testing

2010-05-05 Thread Christopher Samuel
On 04/05/10 10:53, Ashley Pittman wrote: > I'm surprised by Samuels description of the problem > because it's not how I remember it and from what Chris > says it doesn't reflect what is in linux Git code either. Actually I think it was Ethan who reported the problem and that was on a Solaris syst

Re: [OMPI devel] System V Shared Memory forOpenMPI:Request forCommunity Input and Testing

2010-05-05 Thread Terry Dontje
Jeff Squyres wrote: On May 4, 2010, at 9:53 AM, Ashley Pittman wrote: Point noted. But actually -- can you give specific reasons as to why a user should care? Keep in mind that this would be a short-lived fork'ed process -- not "spawn" in the MPI sense of the word. You might be r

Re: [OMPI devel] System V Shared Memory forOpenMPI:Request forCommunity Input and Testing

2010-05-05 Thread Jeff Squyres
On May 4, 2010, at 9:53 AM, Ashley Pittman wrote: > > Point noted. But actually -- can you give specific reasons as to why a > > user should care? Keep in mind that this would be a short-lived fork'ed > > process -- not "spawn" in the MPI sense of the word. > > You might be running the job un