From: Clint Adams <schizo@debian.org>
To: ZSH-workers@sunsite.auc.dk
Subject: PATCH: mmap error
Date: Mon, 31 Jan 2000 13:35:46 -0500 [thread overview]
Message-ID: <20000131133546.A13537@dman.com> (raw)
This is not an elegant solution. Of course, I'm not even sure that it works.
The point is to not segfault after mmap failure.
Index: Src/mem.c
===================================================================
RCS file: /cvs/zsh/zsh/Src/mem.c,v
retrieving revision 1.1.1.14
diff -u -r1.1.1.14 mem.c
--- Src/mem.c 2000/01/20 09:01:44 1.1.1.14
+++ Src/mem.c 2000/01/31 18:21:46
@@ -356,6 +356,7 @@
n = (n + pgsz) & ~pgsz;
h = (Heap) mmap(NULL, n, PROT_READ | PROT_WRITE,
MMAP_FLAGS, -1, 0);
+ if(h==-1) { perror("mmap error"); exit;}
h->size = n;
}
#else
next reply other threads:[~2000-01-31 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-31 18:35 Clint Adams [this message]
2000-02-01 18:45 ` Peter Stephenson
2000-02-01 20:53 ` Peter Stephenson
2000-02-01 13:07 Sven Wischnowsky
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=20000131133546.A13537@dman.com \
--to=schizo@debian.org \
--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).