<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Am 2015-07-19 um 10:56 schrieb Jay K:<br>
</div>
<blockquote cite="mid:COL130-W32C4709A9C9DBF9CCB035AE6860@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">
<div>Merely subtracting the stack pointer isn't correct on all
systems.</div>
<div>At least on NT, stack pages must be touched in order
without skipping any,</div>
<div>for stack overflow exceptions to work correctly.</div>
<div>There is a high water mark, so it isn't necessarily linear.</div>
</div>
</blockquote>
<br>
Would that mind if the stack exception was generated somewhat <br>
later when the jumpbuf actually becomes accessed?<br>
I would believe no.<br>
<br>
<blockquote cite="mid:COL130-W32C4709A9C9DBF9CCB035AE6860@phx.gbl"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>NEWA: alloca is considered kind of dangerous, in that
failure</div>
<div>is difficult to recognize, or not portably recognizable and
handlable.</div>
</div>
</blockquote>
<br>
The same stack overflow exception can be generated by any <br>
procedure call so that I do not see why it should be that <br>
dangerous. In the overwhelming majority of cases this should<br>
be handled as gracefully as an extension of the heap on NEW:<br>
simply map a new memory page as long as there is enough<br>
free virtual address space.<br>
<br>
<br>
<blockquote cite="mid:COL130-W32C4709A9C9DBF9CCB035AE6860@phx.gbl"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>If people can do the work/research/testing for recognizing
stack exhaustion</div>
<div>on a decent set of systems -- Linux, Solaris, FreeBSD,
OpenBSD, NetBSD, NT,</div>
<div>possibly AIX, OpenVMS, Irix, HP-UX -- then this would grain
traction in my mind.</div>
</div>
</blockquote>
As we are planning a new realease I would believe that your new <br>
alterations would become tested shortly.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>