Groups > comp.os.os2.programmer.misc > #238

Re: Avoiding recursive stack overflow in C?

From	Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
Newsgroups	comp.unix.programmer, comp.lang.c, comp.os.ms-windows.programmer.win32, comp.os.os2.programmer.misc
Subject	Re: Avoiding recursive stack overflow in C?
References	(8 earlier) <iq3fs7$pc7$1@dont-email.me> <c8e8e850-aa1a-4dd3-9f58-94ed708d25a8@z13g2000yqg.googlegroups.com> <iq50gu$46r$1@dont-email.me> <IU.D20110515.T160558.P4093.Q0@J.de.Boyne.Pollard.localhost> <iqp4od$1mk$1@dont-email.me>
Message-ID	<IU.D20110515.T215017.P4453.Q0@J.de.Boyne.Pollard.localhost> (permalink)
Organization	virginmedia.com
Date	2011-05-15 22:49 +0100

Cross-posted to 4 groups.

Show all headers | View raw

>>> [...] Where's the buzzer/warning light for approaching the stack 
>>> limits in C? The non-portable best that I can do is handling 
>>> SIGSEGV, which is a little late; the problem I wanted to avoid has 
>>> already happened by the time that signal is raised. For that matter, 
>>> I'd settle for the analog of a gas gauge - where can I find it?
>>>
>> For what it's worth, if you expand your horizons outside of just Unix 
>> and Linux, things are rather different.
>>
> My horizon is a lot larger than that, which is why a Windows-specific 
> solution is just as unhelpful to me as a Unix-specific one.
>
You weren't given a Windows-specific solution.  Go and read what I 
wrote, but properly this time, instead of stopping after the first 
sentence as you did above.  Your horizons certainly in this thread so 
far have most definitely been confined to Unix and Linux.  You keep 
going on about SIGSEGV, for starters.  If your horizon were wider, you'd 
not be doing so.  Nor would you be bringing up as problems things that 
simply aren't the case outwith the narrow confines of Unix and Linux.  
And indeed, I quote you from a couple of messages back:

> My own programs are allowed to assume [...] a correspondingly early 
> version of POSIX, [...]
>
There's that narrow horizon right there, in your very own words.

Thread

Re: Avoiding recursive stack overflow in C? Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2011-05-15 17:05 +0100
  Re: Avoiding recursive stack overflow in C? James Kuyper <jameskuyper@verizon.net> - 2011-05-15 14:07 -0400
    Re: Avoiding recursive stack overflow in C? Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2011-05-15 22:49 +0100
      Re: Avoiding recursive stack overflow in C? James Kuyper <jameskuyper@verizon.net> - 2011-05-15 21:08 -0400
      Re: Avoiding recursive stack overflow in C? Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-05-16 11:10 +0100
  Re: Avoiding recursive stack overflow in C? Ilya Zakharevich <nospam-abuse@ilyaz.org> - 2011-05-16 08:04 +0000

csiph-web