./devel/electric-fence, Different kind of malloc() debugger

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: pkgsrc-2012Q1, Version: 2.1.13.0.1nb1, Package name: electric-fence-2.1.13.0.1nb1, Maintainer: pkgsrc-users

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.


Required to build:
[devel/libtool-base]

Master sites:

SHA1: e6765bcb1543272040b806eea706fc7ae9b60524
RMD160: 75e41de7bef263007f24a1053528959f9f7fe1fa
Filesize: 29.288 KB

Version history: (Expand)

CVS history: (Expand)


   2012-06-19 00:18:35 by Matthias Scheler | Files touched by this commit (3) 
Log message:
Pullup ticket #3835 - requested by dholland
devel/electric-fence: build fix

Revisions pulled up:
- devel/electric-fence/Makefile                                 1.4
- devel/electric-fence/distinfo                                 1.2
- devel/electric-fence/patches/patch-efence_c                   1.1

---
   Module Name:	pkgsrc
   Committed By:	dholland
   Date:		Sat Jun 16 07:46:55 UTC 2012

   Modified Files:
   	pkgsrc/devel/electric-fence: Makefile distinfo
   Added Files:
   	pkgsrc/devel/electric-fence/patches: patch-efence_c

   Log message:
   Add gcc memory barriers after the manner of emacs20's patch-bm, for
   the same reason: gcc "knows" that malloc has no side effects and
   reorders code around it, only it's wrong. Fixes SIGSEGV during build
   seen in some environments.

   Bump package revision as a precaution, because I don't understand why
   this sometimes doesn't fail and sometimes does with the same gcc
   version.