Size zero allocations

Size zero allocations

[Bart Schaefer]

Press kill-whole-line at an empty prompt, and ElectricFence reports:

zagzig% ^U
ElectricFence Aborting: Allocating 0 bytes, probably a bug.

Is this, in fact, a bug?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   

Re: Size zero allocations

[Dan Nelson]

In the last episode (Mar 06), Bart Schaefer said:
> Press kill-whole-line at an empty prompt, and ElectricFence reports:
> 
> zagzig% ^U
> ElectricFence Aborting: Allocating 0 bytes, probably a bug.
> 
> Is this, in fact, a bug?

Probably.  The Single Unix specs read:

    If the size of the space requested is 0, the behaviour is
    implementation-dependent; the value returned will be either a null
    pointer or a unique pointer.

FreeBSD's malloc can be configured to return either (it defaults to
returning a pointer to a 0-byte malloc structure), and comments:

    It can be argued that returning a null pointer when asked to
    allocate zero bytes is a silly response to a silly question.

Tru64 returns NULL, and Solaris 8's manpage seems to imply that it
returns a pointer.

-- 
	Dan Nelson
	dnelson@emsphone.com

Re: Size zero allocations

[Sven Wischnowsky]

Bart Schaefer wrote:

> Press kill-whole-line at an empty prompt, and ElectricFence reports:
> 
> zagzig% ^U
> ElectricFence Aborting: Allocating 0 bytes, probably a bug.
> 
> Is this, in fact, a bug?

Well, adding an empty string to the kill ring doesn't seem to make
much sense... maybe we should just add a `if (!ct) return;' to cut()
(in zle_utils.c)?

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de

Re: Size zero allocations

[Bart Schaefer]

On Mar 7, 11:09am, Sven Wischnowsky wrote:
}
} Bart Schaefer wrote:
} > Press kill-whole-line at an empty prompt
} 
} Well, adding an empty string to the kill ring doesn't seem to make
} much sense... maybe we should just add a `if (!ct) return;' to cut()
} (in zle_utils.c)?

I'm in favor of this.