X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: [FAQ alert] RE: segfault on memory intensive programs Date: Thu, 30 Mar 2006 15:57:40 +0100 Message-ID: <067601c6540a$4a5be3a0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20060330144928.29544.qmail@web34811.mail.mud.yahoo.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 30 March 2006 15:49, Pete wrote: > --- Dave Korn wrote: Pete, please don't do ^^^^^^^^^^ that. If you quote someone's email address in raw text, it gets archived on the mailinglist web archive, and then spam-harvesters get it, and then that person gets a BOATLOAD more spam. Please read http://cygwin.com/acronyms#PCYMTNQREAIYR for more. > BTW, is there a corresponding way of specifying the > stack size using registry settings? That link only > mentions heap settings. Not that I know of. > I implement large financial models, and will need a > larger stack for everything I do. It would be nice to > set it in the registry once rather than put the same > LDFLAG variable in every Makefile I write (and comment > it out when I take my code home to work on it at night > on my Linux box). Well, if it was a registry setting then your binaries wouldn't run on any other pc without editing the registry of that pc as well, so it's just as well that stack size is specified in the headers in the .exe rather than in every single machine that ever needs to run the exe. It's also not recommended programming style to place huge objects on the stack. For best results they should be static or malloced. But this is all generic programming advice and nothing to do with cygwin per se, so it's getting off-topic now. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/