Except in my recent experiences the ONLY clearly insufficient stack space errors I have received come back to one of two things... 1)PHP and 2) the glibc upgrade in redhat doing something funky to the memory requirements causing DNS lookups (al la hosts.allow in nsperm or gethostbyaddr)...
This tells me that writing bad code in TCL isn't the only way, or even the most prolific way that happens in the "real world" that I have seen.. thus it would be a good idea to at least attempt to signal that the stack space is insufficient.. heck, even a "high water mark" procedure that you can turn on that could be accessed the same way other stuff is in nstelemetry.adp would be a benifit.. because then we could just keep an eye on that value as a guideline when to consider upping the value. Heck, even Borland Pascal from the dos age tried (emphasis on tried) to handle stack issues gracefully... so why not aolserver? -- Patrick Spence <arivenATarivenDOTcom> www.RandomRamblings.com www.Ariven.com ----- Original Message ----- From: "Jeff Hobbs" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 01, 2002 3:52 PM Subject: Re: [AOLSERVER] crashes related to insufficient stack space > > is there any way to catch crashes related to insufficient stack space and > add > > a relevant entry in the server log to remove the guesswork from > > troubleshooting these? > > These are most often related to infinite loops in Tcl. In general the > recursion limit (default 1000 - note that this is for infinite loop > recursion, and as such is fairly high) is not too high to be caught > without blowing stack. However, AOLServer uses a threaded Tcl, and many > machines have a much lower per-thread stack. You can either up this, or, > starting in Tcl 8.4, lower the recursion limit (via interp recusionlimit) > in order to move the problem back into being a Tcl error (not a crash). > > Jeff Hobbs The Tcl Guy > Senior Developer http://www.ActiveState.com/ > Tcl Support and Productivity Solutions
