diff options
Diffstat (limited to 'devel/electricfence/pkg')
| -rw-r--r-- | devel/electricfence/pkg/COMMENT | 1 | ||||
| -rw-r--r-- | devel/electricfence/pkg/DESCR | 7 | ||||
| -rw-r--r-- | devel/electricfence/pkg/PLIST | 3 |
3 files changed, 11 insertions, 0 deletions
diff --git a/devel/electricfence/pkg/COMMENT b/devel/electricfence/pkg/COMMENT new file mode 100644 index 00000000000..07abc4e94ae --- /dev/null +++ b/devel/electricfence/pkg/COMMENT @@ -0,0 +1 @@ +a different kind of malloc() debugger. diff --git a/devel/electricfence/pkg/DESCR b/devel/electricfence/pkg/DESCR new file mode 100644 index 00000000000..dccc91bf84b --- /dev/null +++ b/devel/electricfence/pkg/DESCR @@ -0,0 +1,7 @@ +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. diff --git a/devel/electricfence/pkg/PLIST b/devel/electricfence/pkg/PLIST new file mode 100644 index 00000000000..addc5f7ef4b --- /dev/null +++ b/devel/electricfence/pkg/PLIST @@ -0,0 +1,3 @@ +@comment $NetBSD: PLIST,v 1.1.1.1 1998/10/27 04:04:11 garbled Exp $ +lib/libefence.a +man/man3/libefence.3 |