From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: zsh exhausting swap
Date: Mon, 13 Sep 1999 12:49:13 +0200 (MET DST) [thread overview]
Message-ID: <199909131049.MAA14081@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Thu, 9 Sep 1999 17:00:43 +0000
Bart Schaefer wrote:
> The crash eventually occurs when a buffer as large as zsh needs cannot
> be allocated.
>
> However, I don't understand what you expect zsh to do differently.
One problem is that sizeline() doens't test if it gets a NULL back
from `realloc()'.
The problem is that we would have to add error-catching code to all
places where this is used...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-09-13 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 10:49 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-08 15:25 Brad Forschinger
1999-09-08 17:19 ` Mike Fletcher
1999-09-09 17:00 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199909131049.MAA14081@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).