Re: Big stack HUGE coredump

2008-02-26 Thread Alexander Nasonov
Mark Kettenis wrote: > Does the attached diff fix your problem? Yes, it does. Thanks! -- Alexander Nasonov

Re: Big stack HUGE coredump

2008-02-25 Thread Mark Kettenis
> Date: Sat, 23 Feb 2008 13:58:55 + > From: Alexander Nasonov <[EMAIL PROTECTED]> > > Hi, > If I set a core limit to "unlimited" and a stack limit to 32768, > then run a program with indefinite recursion, the system would > generate 8G coredump file. Does the attached diff fix your problem?

Re: Big stack HUGE coredump

2008-02-23 Thread Alexander Nasonov
Stefan Kell wrote: > just curious: what problem do you want to correct? 8GB coredump is surely > a big file but so is ulimit -s 32768. This ulimit means 32768 x 1024 bytes > for stack as you probably know and this is the exact amount which is shown > in the coredump (33.554.432 = 32768x1024). 8G

Re: Big stack HUGE coredump

2008-02-23 Thread Stefan Kell
Hello, just curious: what problem do you want to correct? 8GB coredump is surely a big file but so is ulimit -s 32768. This ulimit means 32768 x 1024 bytes for stack as you probably know and this is the exact amount which is shown in the coredump (33.554.432 = 32768x1024). Regards Stefan Ke

Big stack HUGE coredump

2008-02-23 Thread Alexander Nasonov
Hi, If I set a core limit to "unlimited" and a stack limit to 32768, then run a program with indefinite recursion, the system would generate 8G coredump file. Here we go: $ uname -a OpenBSD obx1000 4.2 GENERIC#375 i386 $ ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited core