Be sure to read this thread in order -- the conclusion of the thread
was that we now actually *do* return NULL, per POSIX advice.
On Jul 25, 2007, at 10:52 AM, Lisandro Dalcin wrote:
> On 7/23/07, Jeff Squyres <jsquyres_at_[hidden]> wrote:
>> I think that this will require a little tomfoolery to fix properly
>> because we can't simply return NULL (you can't expect to use the
>> pointer that we return to store anything, but you should be able to
>> expect to be able to dereference it without seg faulting).
>
> Excellent! As reference, MPICH2 seems to return different pointers for
> size=0, but perhaps this happens because it falls to use system
> malloc, and in my box this always return different, non-null pointers.
>
> --
> Lisandro Dalcín
> ---------------
> Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
> Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
> Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
> PTLC - Güemes 3450, (3000) Santa Fe, Argentina
> Tel/Fax: +54-(0)342-451.1594
>
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
--
Jeff Squyres
Cisco Systems
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}