Stephane Eranian wrote:
Hi,
On Sun, Mar 25, 2007 at 06:30:34PM +0200, Folkert van Heusden wrote:
I'd say "feature", glibc's malloc also returns an address on
malloc(0).
This is implementation defined-the standard allows for return of either
null or an address.
Entirely for entertainment:
Stephane Eranian wrote:
Hi,
On Sun, Mar 25, 2007 at 06:30:34PM +0200, Folkert van Heusden wrote:
I'd say feature, glibc's malloc also returns an address on
malloc(0).
This is implementation defined-the standard allows for return of either
null or an address.
Entirely for entertainment: AIX
Hi,
On Sun, Mar 25, 2007 at 06:30:34PM +0200, Folkert van Heusden wrote:
> > > I'd say "feature", glibc's malloc also returns an address on
> > > malloc(0).
> > >
> > This is implementation defined-the standard allows for return of either
> > null or an address.
>
> Entirely for entertainment:
Hi,
On Sun, Mar 25, 2007 at 06:30:34PM +0200, Folkert van Heusden wrote:
I'd say feature, glibc's malloc also returns an address on
malloc(0).
This is implementation defined-the standard allows for return of either
null or an address.
Entirely for entertainment: AIX (5.3) returns
> > I'd say "feature", glibc's malloc also returns an address on
> > malloc(0).
> >
> This is implementation defined-the standard allows for return of either
> null or an address.
Entirely for entertainment: AIX (5.3) returns NULL, IRIX returns a valid
address.
Folkert van Heusden
--
I'd say feature, glibc's malloc also returns an address on
malloc(0).
This is implementation defined-the standard allows for return of either
null or an address.
Entirely for entertainment: AIX (5.3) returns NULL, IRIX returns a valid
address.
Folkert van Heusden
--
MultiTail är en
On Thu, 22 Mar 2007, Stephane Eranian wrote:
> I ran into an issue with perfmon where I ended up calling
> kmalloc() with a size of zero. To my surprise, this did
> not return NULL but a valid data address.
>
> I am wondering if this is a property of kmalloc() or simply
> a bug. It is the case
On Thu, 22 Mar 2007, Stephane Eranian wrote:
I ran into an issue with perfmon where I ended up calling
kmalloc() with a size of zero. To my surprise, this did
not return NULL but a valid data address.
I am wondering if this is a property of kmalloc() or simply
a bug. It is the case that
On Fri, 2007-03-23 at 07:08 +0530, Jan Engelhardt wrote:
>
> On Mar 22 2007 16:18, Stephane Eranian wrote:
> >
> I'd say "feature", glibc's malloc also returns an address on
> malloc(0).
>
This is implementation defined-the standard allows for return of either
null or an address.
>
> Jan
> --
>
On Mar 22 2007 16:18, Stephane Eranian wrote:
>
>Hello,
>
>I ran into an issue with perfmon where I ended up calling
>kmalloc() with a size of zero. To my surprise, this did
>not return NULL but a valid data address.
>
>I am wondering if this is a property of kmalloc() or simply
>a bug. It is the
Hello,
I ran into an issue with perfmon where I ended up calling
kmalloc() with a size of zero. To my surprise, this did
not return NULL but a valid data address.
I am wondering if this is a property of kmalloc() or simply
a bug. It is the case that the __kmalloc() code does not
check for zero
Hello,
I ran into an issue with perfmon where I ended up calling
kmalloc() with a size of zero. To my surprise, this did
not return NULL but a valid data address.
I am wondering if this is a property of kmalloc() or simply
a bug. It is the case that the __kmalloc() code does not
check for zero
On Mar 22 2007 16:18, Stephane Eranian wrote:
Hello,
I ran into an issue with perfmon where I ended up calling
kmalloc() with a size of zero. To my surprise, this did
not return NULL but a valid data address.
I am wondering if this is a property of kmalloc() or simply
a bug. It is the case
On Fri, 2007-03-23 at 07:08 +0530, Jan Engelhardt wrote:
On Mar 22 2007 16:18, Stephane Eranian wrote:
I'd say feature, glibc's malloc also returns an address on
malloc(0).
This is implementation defined-the standard allows for return of either
null or an address.
Jan
--
-
To
14 matches
Mail list logo