Date: Sun, 16 Feb 1997 18:12:12 -0800 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: cschuber@uumail.gov.bc.ca, Bruce Evans <bde@zeta.org.au> Cc: dufault@hda.com, roberto@keltia.freenix.fr, freebsd-security@FreeBSD.org Subject: Re: buffer overruns Message-ID: <199702170212.SAA23186@salsa.gv.tsc.tdk.com> In-Reply-To: Cy Schubert <cy@cwsys.cwent.com> "Re: buffer overruns" (Feb 16, 1:05pm)
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 16, 1:05pm, Cy Schubert wrote: } Subject: Re: buffer overruns } } What about the bounds-checking gcc? Would that be a place to start? } You can get it from ftp://dse.doc.ic.ac.uk/pub/misc/bcc/. I'm using it for something right now, but it's not a general purpose solution. It doesn't get along very well with signals. Your code will run about 20 times slower. It works really well in those cases where your software manages to corrupt large parts of its memory before finally core dumping, so that you can't figure out what caused the initial problem by pointing gdb at the core dump. --- Truck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702170212.SAA23186>