From: Bill Priest <priestwilliaml@yahoo.com>
To: cygwin@cygwin.com
Cc: jek-cygwin1@kleckner.net
Subject: jek-cygwin1@kleckner.net (bounds checking)
Date: Mon, 13 Dec 2004 01:18:00 -0000 [thread overview]
Message-ID: <20041213011810.91265.qmail@web20824.mail.yahoo.com> (raw)
Jim & All,
I've successfully built and used cygwin 3.3.1 with
Herman Ten Brugge's bounds checking patches. I've
submitted the trivial changes required for cygwin back
to Herman.
You can google for Herman Ten Brugge and find a
reference to the changes I made to get them to work
w/ cygwin.
Of course it only works w/ 'C'; but I used it to
track down array indexing problems and pointer
problems.
FYI,
Bill
__________________________________
Do you Yahoo!?
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2004-12-13 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 1:18 Bill Priest [this message]
2004-12-17 20:45 ` gcc bounds checking, valgrind, purify Jim Kleckner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041213011810.91265.qmail@web20824.mail.yahoo.com \
--to=priestwilliaml@yahoo.com \
--cc=cygwin@cygwin.com \
--cc=jek-cygwin1@kleckner.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).