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 83111 - efence broken on Hammer
efence broken on Hammer
Product: Red Hat Raw Hide
Classification: Retired
Component: ElectricFence (Show other bugs)
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
Blocks: 79579
  Show dependency treegraph
Reported: 2003-01-30 08:40 EST by Joe Orton
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-04 11:42:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joe Orton 2003-01-30 08:40:17 EST
Description of problem:
ElectricFence dumps core on Hammer immediately at startup.

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

How reproducible:

Steps to Reproduce:
$ ef ls

anything linked against -lefence does likewise, as does running the test suite
in the EF sources.

Actual results:

  Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens <bruce@perens.com>
/usr/bin/ef: line 20:  1132 Segmentation fault      ( export
LD_PRELOAD=libefence.so.0.0; exec $* )

Expected results:
No segfaults.

Additional info:
EF test suite passes if not compiled with -DUSE_SEMAPHORE.
From adding debugging, the segfault occurs in exactly the pthread_self() call in
Comment 1 Joe Orton 2003-01-30 08:57:57 EST
(As an aside, efence.c seems to assume 0 isn't a valid pthread_t, which I don't
believe is correct, and it probably should be using pthread_equal rather than !=
to compare pthread_t values.  Neither of these seem to be the cause of the
segfaults, however.)
Comment 2 Jakub Jelinek 2003-02-04 11:42:31 EST
Should be fixed in ElectricFence-2.2.2-15.
Comment 3 Joe Orton 2003-02-04 11:55:33 EST
Thanks Jakub, works fine for me now.

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