Date: Sun, 11 Apr 2004 11:29:57 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Ted Unangst <tedu@stanford.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD and Debugging? Message-ID: <20040411162941.GA1319@dan.emsphone.com> In-Reply-To: <Pine.GSO.4.44.0404101502460.5306-100000@elaine29.Stanford.EDU> References: <6.0.2.0.2.20040409230629.01cc1ec0@mx1.erhartgroup.com> <Pine.GSO.4.44.0404101502460.5306-100000@elaine29.Stanford.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Apr 10), Ted Unangst said: > On Fri, 9 Apr 2004, Brandon Erhart wrote: > > Are there any debuggers out there for BSD that will detect the > > heap/stack corruption!? > > valgrind and electric fence are very good suggestions. my own > personal pet project was adding guard pages to the system malloc. > then linking malloc.conf -> AFGJ or setenv MALLOC_OPTIONS and you can > find bugs in all the software you run. it's less complete than a > dedicated heap checker, but lightweight enough (well, 20% penalty may > not be light for some) that i run with it full time. we've had a > fairly significant amount of success with it finding bugs in software > that just happened to work. > > http://www.zeitbombe.org/patches/malloc_guard.diff should apply pretty > cleanly to freebsd's malloc.c I also have a malloc debugging patch that changes the Junk flag to fill with a counter value, so you can track down where in your program a particular block of memory was allocated/freed. http://dan.allantgroup.com/FreeBSD/malloc.diff , or PR 52907 -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040411162941.GA1319>