Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: valgrind: useful memory checker
- X-seq: zsh-workers 17022
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Felix Rosencrantz <f_rosencrantz@xxxxxxxxx>
- Subject: Re: valgrind: useful memory checker
- Date: Mon, 22 Apr 2002 11:32:35 -0700 (PDT)
- Cc: zsh-workers <zsh-workers@xxxxxxxxxxxxxx>, Julian Seward <jseward@xxxxxxx>
- In-reply-to: <20020422182026.19547.qmail@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- Sender: schaefer@xxxxxxxxxxxxxxxx
On Mon, 22 Apr 2002, Felix Rosencrantz wrote:
> One of the problems was that zsh calls malloc() during signal handlers.
> Which Julian pointed out is not a particularly safe thing to do.... (I
> figure Bart or others might comment about this.)
It's "not particularly safe" only if you don't know what you're doing.
We went to some trouble a while ago to assure that signals are blocked
while zsh is performing other memory allocations, so that we don't have
re-entry problems with calling malloc() from inside the handlers when they
do get called.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author