From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randolph Chung Subject: Re: [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1 Date: Tue, 16 Aug 2005 18:10:24 +0800 Message-ID: <4301BB90.5060907@tausq.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: "James.Bottomley" , dave , parisc-linux , tsg45800 To: Joel Soete Return-Path: In-Reply-To: List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: parisc-linux-bounces@lists.parisc-linux.org > on a b180 model runing the latest cvs 2.6.13-rc6-pa1 (compiled with debian > stock gcc-4.0, as it's an unstable install but downgraded libc6 2.3.2), foo > runs untils: > ... > Estimating stack consumed 0x7fee40 > Estimating stack consumed 0x7fef80 > Estimating stack consumed 0x7ff0c0 > ======= > > The ping still responding but not anymore the console (nor other process > apparently)... no more heartbit/disk leds flashing; pressing TOC buton launch > the reboot but what is bad: nothing was saved in piminfo (all 0 and No valid > timestamp) :-( Yup, this is the same as what others are seeing. It's definitely a problem with infinitely looping signal handlers. I'm not sure what's the "correct" behavior in this case. I recall now that we saw a similar problem with expect where the signal handler was recursing. Is the kernel responsible for blocking SIGSEGV handlers that generate SIGSEGV? randolph _______________________________________________ parisc-linux mailing list parisc-linux@lists.parisc-linux.org http://lists.parisc-linux.org/mailman/listinfo/parisc-linux