Date: Wed, 12 Feb 1997 23:11:01 -0500 (EST) From: Ken Wong <wong@a17b32.rogerswave.ca> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: "Daniel O'Callaghan" <danny@panda.hilink.com.au>, hackers@freebsd.org Subject: Re: strlen() question, maybe str*cpy Message-ID: <Pine.BSF.3.91.970212230555.242B-100000@wong.rogerswave.ca> In-Reply-To: <Mutt.19970212095452.j@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Feb 1997, J Wunsch wrote: > Why? The worst that would happen by touching off the end of your > address space is a SIGSEGV. The problem with str*cpy() touching > beyond the bounds of their arrays is that they can _modify_ the stack > then, but that can't happen with strlen() since it doesn't modify > anything. why isn't the str*cpy check the BP (base pointer?) register and use it to gaurd against stack over right? Ken
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970212230555.242B-100000>