Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 143395 - ElectricFence aborts
ElectricFence aborts
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: grep (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-12-20 06:43 EST by Tim Waugh
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-19 23:25:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
file (2.64 KB, text/plain)
2004-12-20 06:43 EST, Tim Waugh
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:449 normal SHIPPED_LIVE Updated grep package 2005-05-19 00:00:00 EDT

  None (edit)
Description Tim Waugh 2004-12-20 06:43:13 EST
Description of problem:
Running grep under ElectricFence can show a zero-byte malloc.

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

How reproducible:

Steps to Reproduce:
1. Install ElectricFence
2. Save attachment as "file"
3. cat file | ef grep -v UND
Actual results:
ElectricFence Aborting: Allocating 0 bytes, probably a bug.
/usr/bin/ef: line 20:  9932 Illegal instruction     ( export
LD_PRELOAD=libefence.so.0.0; exec $* )

Expected results:
Doesn't abort.

Additional info:
Comment 1 Tim Waugh 2004-12-20 06:43:13 EST
Created attachment 108886 [details]
Comment 2 Tim Waugh 2004-12-20 06:55:58 EST
grep-2.5.1-24.3 does not exhibit the problem.
Comment 3 Dennis Gregorovic 2005-05-19 23:25:55 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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