Re: Command died with status 134

On 2015-08-05 09:16 +0200, Eric Smith wrote:

> Command died with status 134: "/usr/bin/procmail -a
> "$EXTENSION"". Command output: Aborted

So procmail dies from the SIGABORT signal.  AFAIK that can only happen
if a program calls abort(2) of its own volition.  So it should be
possible to isolate all the possibilities by looking at procmail
source.  To be sure, there may be many, probably in reaction to any
syscall failure.  But I would imagine in most of those cases procmail
would log some other info to stderr or the logfile.  If you don't see
anything specific in the logfile you can just focus on abort() calls not
preceded by such log activity.

-- 
Please *no* private copies of mailing list or newsgroup messages.
Rule 420: All persons more than eight miles high to leave the court.