X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 15 Apr 2010 10:54:22 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Disabling *.stackdump ? Message-ID: <20100415145422.GC23436@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4BC65340 DOT 8040701 AT gmail DOT com> <20100415082924 DOT GA7865 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100415082924.GA7865@calimero.vinschen.de> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 Thu, Apr 15, 2010 at 10:29:24AM +0200, Corinna Vinschen wrote: >On Apr 15 09:44, Rurik Christiansen wrote: >> Hi, >> >> Is there a way to disable the stackdump ? ('ulimit -c 0' doesn't seem to >> do the trick) > >The only way to disable stackdumps right now is to use the respective >setrlimit(RLIMIT_CORE, ...) call within the application itself. It's >not one of the variables propagated to any child process. > >However, that shouldn't be too hard to change, we just have to move the >internal variable keeping track of this value, rlim_core, into the >cygheap. > >Chris? That should be all, right? That's what I was thinking yes. You want me to do it or do you already have something? cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple