This is the mail archive of the
mailing list for the Cygwin project.
gcc bounds checking, valgrind, purify
- From: Jim Kleckner <jek-cygwin1 at kleckner dot net>
- To: cygwin at cygwin dot com
- Cc: Bill Priest <priestwilliaml at yahoo dot com>
- Date: Fri, 17 Dec 2004 12:44:45 -0800
- Subject: gcc bounds checking, valgrind, purify
- References: <email@example.com>
Bill Priest wrote:
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
You can google for Herman Ten Brugge and find a
reference to the changes I made to get them to work
Of course it only works w/ 'C'; but I used it to
track down array indexing problems and pointer
Very interesting. Checking out those links, it appears
that these patches are very much like a static version
of Valgrind. Valgrind works dynamically with an x86
code rewriter that appears to be language independent
and seems to implement a lot of the difficult functionality
that the original Purify implemented. Valgrind ought
to work with C++ where gcc-bounds-checking as you
say is only 'C' (though there are some traces in
These patches have been around for 10 years (!).
This kind of test is so valuable, I'm surprised that
they have never been integrated into gcc. It seems
like it isn't such a big risk to include them and
config them to be off by default. This would
hugely improve the maintainability and availability
of the patches.
Did your cygwin patches get into bounds checking
patch for the 3.4.2-100 version of 7-Sep-2004 ?
It does look so from the source.
Would it be reasonable integrate this patch into
the cygwin GCC? I expect back the answer no,
because GCC needs to be synced with the upstream.
But this stuff would be so much more valuable if
(in order of accessibility):
- It was just part of GCC as an option
- It could be selectively installed as a package alternative
- The patches were integrated so that one could download
There was a discussion here:
about the value of recompiling sort of a "super debug"
version of the cygwin dll and libraries with gcc-bounds-checking
that ran slowly but did a lot of checking. That would indeed
PS: Please don't put my email address in the subject line.
Spam harvesters, you know.
PPS: Convenience links for fellow travelers:
Good article giving the context and pointers:
GCC extensions page:
Herman Ten Brugge pages with source:
Alternate (main?) source of the patches:
Valgrind home page:
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html