summaryrefslogtreecommitdiff
path: root/open_issues/code_analysis.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2012-11-27 22:30:22 +0100
committerThomas Schwinge <thomas@codesourcery.com>2012-11-27 22:30:22 +0100
commitae1cc0d932c8bb939fa2037e6183c1ce8f550942 (patch)
treed86ac5a03830f27112a61714a5ab1a74fcd760e5 /open_issues/code_analysis.mdwn
parent5cc8714e4af82bec2ad7ea2d2479016e5a74de9b (diff)
open_issues/code_analysis: MALLOC_CHECK_, MALLOC_PERTURB_.
Diffstat (limited to 'open_issues/code_analysis.mdwn')
-rw-r--r--open_issues/code_analysis.mdwn31
1 files changed, 19 insertions, 12 deletions
diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn
index fd8a36de..b3908243 100644
--- a/open_issues/code_analysis.mdwn
+++ b/open_issues/code_analysis.mdwn
@@ -103,18 +103,25 @@ There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks.
* <https://wiki.ubuntu.com/CompilerFlags>
- * 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.
+ * `MALLOC_CHECK_`/`MALLOC_PERTURB_`
+
+ * 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.
+
+ * [`MALLOC_PERTURB_`](http://udrepper.livejournal.com/11429.html)
+
+ * <http://git.fedorahosted.org/cgit/initscripts.git/diff/?id=deb0df0124fbe9b645755a0a44c7cb8044f24719>
* In context of [[!message-id
"1341350006-2499-1-git-send-email-rbraun@sceen.net"]]/the `alloca` issue