Bug 79691 - procmail dumps core
procmail dumps core
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: procmail (Show other bugs)
9
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Jens Petersen
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-15 03:10 EST by Binand Sethumadhavan
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-06-23 00:03:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Binand Sethumadhavan 2002-12-15 03:10:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
when a signal is received, procmail dumps core.

This happens for I think all fatal signals procmail handles.

I tested with SIGINT, SIGTERM and SIGHUP. Procmail dumped core on all three 
occassions.

Typical output when I send a signal from another terminal to a running 
procmail:

binand@binand[~]:(11) procmail
procmail: Terminating prematurely
Segmentation fault (core dumped)


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. run procmail from command line (with or without an rc file)
2. press control-C for SIGINT
3. procmail will dump core, with the above output
    

Actual Results:  lots of core.$$ files in my home directory :)

Expected Results:  procmail should have performed a clean shutdown.

Additional info:
Comment 1 Jens Petersen 2003-08-09 22:25:11 EDT
Reproduced.

Sent a mail to the maintainer for feedback.
Comment 2 Jens Petersen 2004-01-06 03:00:00 EST
This seems to be fixed when Debian's procmail_3.22-8.diff
is applied.

I'm adding that patch to procmail-3.22-12.

Note You need to log in before you can comment on or make changes to this bug.