summaryrefslogtreecommitdiff
path: root/open_issues
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2012-11-21 10:38:04 +0100
committerThomas Schwinge <thomas@codesourcery.com>2012-11-21 10:38:04 +0100
commit61ce0487a68560c58367d3a82f30ab00345cd72f (patch)
tree3959ce5b167608ae8f74bc85bedddd8d557b15e9 /open_issues
parent562782408dd69798f60fd9d343b8f51f56ba2600 (diff)
open_issues/code_analysis: GCC's AddressSanitizer.
Diffstat (limited to 'open_issues')
-rw-r--r--open_issues/code_analysis.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn
index 9089eea4..a7a7031a 100644
--- a/open_issues/code_analysis.mdwn
+++ b/open_issues/code_analysis.mdwn
@@ -127,6 +127,12 @@ There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks.
<youpi> ah, no, the libthreads code properly sets the guard, just for
grow-up stacks
+ * GCC's AddressSanitizer (ASan; `-faddress-sanitizer`)
+
+ [Finding races and memory errors with GCC instrumentation
+ (AddressSanitizer)](http://gcc.gnu.org/wiki/cauldron2012#Finding_races_and_memory_errors_with_GCC_instrumentation_.28AddressSanitizer.29),
+ GNU Tools Cauldron 2012.
+
* Input fuzzing
Not a new topic; has been used (and a paper published) for early UNIX