diff options
author | James Raynard <jraynard@FreeBSD.org> | 1997-11-12 23:46:32 +0000 |
---|---|---|
committer | James Raynard <jraynard@FreeBSD.org> | 1997-11-12 23:46:32 +0000 |
commit | 28a5cee651fd463442f1775e948821c02f24c5d8 (patch) | |
tree | a6df992f8b831b3b5b19930d69cb0150d6c255e3 /devel/ElectricFence/pkg-descr | |
parent | c890f896ed69c8bb8a002736dc8b84a99d70b23d (diff) |
ElectricFence, the debugging malloc library
Notes
Notes:
svn path=/head/; revision=8597
Diffstat (limited to 'devel/ElectricFence/pkg-descr')
-rw-r--r-- | devel/ElectricFence/pkg-descr | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/devel/ElectricFence/pkg-descr b/devel/ElectricFence/pkg-descr new file mode 100644 index 000000000000..7b04b84fb738 --- /dev/null +++ b/devel/ElectricFence/pkg-descr @@ -0,0 +1,15 @@ +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 +libefence.3 . |