From 61ce0487a68560c58367d3a82f30ab00345cd72f Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 21 Nov 2012 10:38:04 +0100 Subject: open_issues/code_analysis: GCC's AddressSanitizer. --- open_issues/code_analysis.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) 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. 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 -- cgit v1.2.3