Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<A7AF87D6496DD411B50A00D0B76DEB2C1E6F5F@EX2BEBREYMBX02>
From:	Darius DOT Clynes AT cec DOT eu DOT int
To:	cygwin AT cygwin DOT com
Subject:	RE: Can I expect electric fence to work?
Date:	Wed, 18 Jul 2001 19:16:45 +0200
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)

yes I have compiled with cygwin against the efence libs for 
memory detection/allocation array bounds, free, etc, problems

it eats tons of memory and produces humungous code
 and goes incredibly slow but you may be able to detect
 a place where allocated memory goes nuts.

 but, it only really works well for memory  explicitly,
  allocated with malloc, so,
 stack corruption, and problems local variables, are not
 easily detected.

 hope you have some molasses ready,
 gdb doesnt especially love efence linked
 exe but it can be done 

>-----Original Message-----
>From: Sengan [mailto:senganb AT ia DOT nsc DOT com]
>Sent: Wednesday, July 18, 2001 3:00 AM
>To: cygwin AT cygwin DOT com
>Subject: Can I expect electric fence to work?
>
>
>I'm actually interested in the functions behind
>efence (mprotect, mmap, etc) to cause a signal
>on memory violations as in efence, but in my own
>program. Can I expect cygwin to be able to do this
>under Windows?
>
>Thanks,
>
>Sengan
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/
>

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -