diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2011-10-03 20:49:54 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2011-10-03 20:49:54 +0200 |
| commit | 219988e74ba30498a1c5d71cf557913a70ccca91 (patch) | |
| tree | 56b85456808cd06e020ef8455ea123c58f624176 /open_issues/code_analysis.mdwn | |
| parent | 278f76de415c83bd06146b2f25a002cf0411d025 (diff) | |
| download | web-219988e74ba30498a1c5d71cf557913a70ccca91.tar.gz web-219988e74ba30498a1c5d71cf557913a70ccca91.tar.bz2 web-219988e74ba30498a1c5d71cf557913a70ccca91.zip | |
IRC.
Diffstat (limited to 'open_issues/code_analysis.mdwn')
| -rw-r--r-- | open_issues/code_analysis.mdwn | 32 |
1 files changed, 24 insertions, 8 deletions
diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn index 552cd2c9..7495221b 100644 --- a/open_issues/code_analysis.mdwn +++ b/open_issues/code_analysis.mdwn @@ -19,7 +19,12 @@ analysis|performance]], [[formal_verification]], as well as general [[!toc]] -# Suggestions +# Bounty + +There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks. + + +# Static * [[GCC]]'s warnings. Yes, really. @@ -52,8 +57,6 @@ analysis|performance]], [[formal_verification]], as well as general * <http://blog.llvm.org/2010/04/whats-wrong-with-this-code.html> - * [[community/gsoc/project_ideas/Valgrind]] - * [Smatch](http://smatch.sourceforge.net/) * [Parfait](http://labs.oracle.com/projects/parfait/) @@ -66,7 +69,12 @@ analysis|performance]], [[formal_verification]], as well as general * [sixgill](http://sixgill.org/) - * [Coverity](http://www.coverity.com/) -- commercial? + * [Coverity](http://www.coverity.com/) (nonfree?) + + +# Dynamic + + * [[community/gsoc/project_ideas/Valgrind]] * <http://en.wikipedia.org/wiki/Electric_Fence> @@ -76,7 +84,15 @@ analysis|performance]], [[formal_verification]], as well as general * <https://wiki.ubuntu.com/CompilerFlags> - -# Bounty - -There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks. + * IRC, freenode, #glibc, 2011-09-28 + + <vsrinivas> two things you can do -- there is an environment variable + (DEBUG_MALLOC_ iirc?) that can be set to 2 to make ptmalloc (glibc's + allocator) more forceful and verbose wrt error checking + <vsrinivas> another is to grab a copy of Tor's source tree and copy out + OpenBSD's allocator (its a clearly-identifyable file in the tree); + LD_PRELOAD it or link it into your app, it is even more aggressive + about detecting memory misuse. + <vsrinivas> third, Red hat has a gdb python plugin that can instrument + glibc's heap structure. its kinda handy, might help? + <vsrinivas> MALLOC_CHECK_ was the envvar you want, sorry. |