Date: Fri, 29 Mar 1996 14:35:43 -0500 (EST) From: owensc <owensc@enc.edu> To: Guy Helmer <ghelmer@alpha.dsu.edu> Cc: questions list FreeBSD <freebsd-questions@freebsd.org> Subject: Re: orphaned proccess hogging CPU (e.g. pine) Message-ID: <Pine.BSF.3.91.960329143236.5915A-100000@dingo.enc.edu> In-Reply-To: <Pine.OSF.3.92.960329111941.2681B-100000@alpha.dsu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Mar 1996, Guy Helmer wrote:
> On Fri, 29 Mar 1996, owensc wrote:
> > Is this CPU-chewing a result of a programming boo-boo in Pine itself? Or
> > is there something system-wide that I should tweak to fix this? I don't
> > mind digging through the source but could use a pointer or two.
>
> Yes, there are a couple of problems in Pine 3.91 where it will hang in a
> loop and eat CPU. One well-known problem was in pine/ttyin.c, where it
> would loop and look for incoming data from the terminal. Another of the
> problems was particularly nasty: pine would set the signal handler for
> SIGSEGV to SIG_IGN (ignore) as it was preparing to exit, and then a bug (I
> hadn't taken the time to track down) made pine SIGSEGV over and over... I
> changed the relevant code in pine/signals.c to never ignore SIGSEGV or
> SIGTERM. I wasn't using the patches provided in the FreeBSD port of pine
> 3.91, so maybe those would have solved my SIGSEGV problem.
Could you possibly post diffs for these modifications, or
describe them at least? (haven't done much signals programming)
thanks very much,
---
-------------------------------------------------------------------------
Charles Owens Email: owensc@enc.edu
"I read somewhere to learn is to
Information Technology Services remember... and I've learned that
Eastern Nazarene College we've all forgot..." - King's X
-------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960329143236.5915A-100000>