bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin

Polley Christopher W PolleyChristopherW@JohnDeere.com
Fri Dec 21 11:56:00 GMT 2001


> -----Original Message-----
> From:	Christopher Faylor [SMTP:cgf@redhat.com]
> On Fri, Dec 21, 2001 at 03:42:14PM +0100, Werner Tuchan wrote:
> >> Weird.  The bytes after EOF are a mixture of NULs and 0xc0.  Is 0xc0
> >> of special significance in Windows?  Is your version of cygwin the
AFAIR, I once read in the book "Code Complete..." by Steve McConnell (a MS
programmer from the pre-windows days) a recommendation to set uninitialized
pointers and memory to a known value (I think he used 0xcccccccc for
pointers and C0 for buffers) to aid in finding bugs of using unitinialized
data areas.  My limited experience with the MS debugger leads me to believe
that this is a practice [at least some of] the MS kernel developers follow.
(BTW, he also advocated setting allocated blocks to another known value
immediately before freeing them, for a similar reason)

Warm Regards,
Chris




--
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/



More information about the Cygwin mailing list