---
name: electricfence
version: 2.2.2_2
origin: devel/ElectricFence
comment: Debugging malloc() that uses the VM hardware to detect buffer overruns
arch: freebsd:9:x86:64
www: UNKNOWN
maintainer: ports@FreeBSD.org
prefix: /usr/local
licenselogic: single
flatsize: 88804
desc: |
  Electric Fence is a different kind of malloc() debugger. It uses the virtual
  memory hardware of your system to detect when software overruns the boundaries
  of a malloc() buffer. It will also detect any accesses of memory that has
  been released by free(). Because it uses the VM hardware for detection,
  Electric Fence stops your program on the first instruction that causes
  a bounds violation. It's then trivial to use a debugger to display the
  offending statement.

  It will probably port to any ANSI/POSIX system that provides mmap(), and
  mprotect(), as long as mprotect() has the capability to turn off all access
  to a memory page, and mmap() can use /dev/zero or the MAP_ANONYMOUS flag
  to create virtual memory pages.

  Complete information on the use of Electric Fence is in the manual page
  efence(3).
categories: [devel]
files:
  /usr/local/bin/ef.sh: 1df9a21468a5cc2bcd9508656c4194826fea70579c1e977799c003868a71a738
  /usr/local/lib/libefence.a: 0a4d33e55794db30b08cc9b239aa6874c3d8e5934f6a182a819540129a3a557b
  /usr/local/lib/libefence.so.0: e5d95a1b290876a8f3cdb1623016f7b5ddd0f8758f9346067b90a9ff53eaa084
  /usr/local/man/man3/efence.3.gz: a6e5d9a9a353810fc59a4027b0cd932f4186bcb1219205b39afe4b3218128f51
scripts:
  post-install: |
    /sbin/ldconfig -m /usr/local/lib
  pre-deinstall: |
    /sbin/ldconfig -R
