[Bug 7898] ps doesn't handle SIGPIPE correctly

bugzilla at busybox.net bugzilla at busybox.net
Tue Mar 3 19:32:53 UTC 2015


https://bugs.busybox.net/show_bug.cgi?id=7898

--- Comment #8 from Aleksey Fedotov <lexa at cfotr.com> 2015-03-03 19:32:52 UTC ---
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > > (In reply to comment #4)
> > > > (In reply to comment #3)
> > > > > This is a bug in debuggerd. It needs to ignore deaths from SIGPIPE and a few
> > > > > other signals (SIGINT, SIGQUIT, SIGABRT).
> > > > 
> > > > Main purpose of debuggerd is to handle unexpected failures in applications and
> > > > if ps crashed with SIGPIPE, then it accounts as 'unexpected'.
> > > 
> > > I disagree. It is an expected failure.
> > 
> > So, if you expect it, why not to set signal handler properly?
> 
> I mean: it is expected for processes to die from SIGPIPE. It is not a bug. It
> was happening in Unix from its early days.
> 
> debuggerd (supposedly) wants to catch BUGS, not normal behavior. Therefore it
> needs to catch signals which indicate bugs: SIGSEGV, SIGBUS, SIGFPE, SIGILL.
> _Not_ SIGPIPE.

SIGPIPE may indicate bug in some cases, but in some it is expected. So If ps is
expected SIGPIPE, why not to handle it properly? Why do you leave signal
handler for SIGPIPE which would trigger debuggerd dump reporting process?

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the busybox-cvs mailing list