From 94a3b7794c94cf2f2c5859eb27be5ffc4a372264 Mon Sep 17 00:00:00 2001
From: garbled <garbled@pkgsrc.org>
Date: Tue, 27 Oct 1998 04:04:11 +0000
Subject: Add new pkg for ElectricFence-2.0.5, a debugging malloc
 implementation.

---
 devel/electricfence/pkg/COMMENT | 1 +
 devel/electricfence/pkg/DESCR   | 7 +++++++
 devel/electricfence/pkg/PLIST   | 3 +++
 3 files changed, 11 insertions(+)
 create mode 100644 devel/electricfence/pkg/COMMENT
 create mode 100644 devel/electricfence/pkg/DESCR
 create mode 100644 devel/electricfence/pkg/PLIST

(limited to 'devel/electricfence/pkg')

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
-- 
cgit v1.2.3