On Apr 15 17:01, Corinna Vinschen wrote:
> On Apr 15 10:54, Christopher Faylor wrote:
> > 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?
>
> No, sorry. I'd be glad if you could do that. I'm so tangled up in the
> tty thingy.
I changed that now. It was a bit more than just moving rlim_core to
cygheap, though.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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
