Bug 15728 - tripwire causing segfault in mail
tripwire causing segfault in mail
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: mailx (Show other bugs)
7.0
i386 Linux
high Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
David Lawrence
:
: 15955 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-08 10:54 EDT by Aaron Brown
Modified: 2005-10-31 17:00 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-11 14:35:30 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 Aaron Brown 2000-08-08 10:54:27 EDT
After I installed from the "qa2" tree built on Aug 7, I keep getting
emails telling me that the tripwire database is not found.  Upon
quitting mail, I get a segfault.
Comment 1 Glen Foster 2000-08-09 09:54:07 EDT
Not a tripwire problem - changing component to "mailx" per Aaron Brown.  The
binary that dumps core is /bin/mail.  Aaron will attach some of the strace
output to this defect ASAP.
Comment 2 Aaron Brown 2000-08-09 10:01:13 EDT
Here is the tail end of the strace I did while exiting
from "mail":


open("/var/spool/mail/root", O_RDONLY)  = 3
fcntl(3, F_GETFL)                       = 0 (flags O_RDONLY)
fstat(3, {st_mode=S_IFREG|0600, st_size=414, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x4001d000
_llseek(3, 0, [0], SEEK_CUR)            = 0
fcntl(3, F_SETFD, FD_CLOEXEC)           = 0
flock(3, LOCK_EX)                       = 0
fstat(3, {st_mode=S_IFREG|0600, st_size=414, ...}) = 0
--- SIGSEGV (Segmentation fault) ---
Comment 3 Jeff Johnson 2000-08-11 14:35:27 EDT
*** Bug 15955 has been marked as a duplicate of this bug. ***
Comment 4 Jeff Johnson 2000-08-11 15:28:12 EDT
I believe this is fixed in mailx-8.1.1-17.

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