diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2012-12-14 11:32:23 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2012-12-14 11:32:23 +0100 |
| commit | d67f6589bf710235ad56731c4c06a75cfad75462 (patch) | |
| tree | eb24a17604d8c090848603d14409a504e9191b7d /open_issues/code_analysis.mdwn | |
| parent | 573d363a3458b8a37e6ec929c778dae8abf90fab (diff) | |
open_issues/gcc: a1d48e100791bc67ff355e0931a604e767c827b7 (2012-12-10; be3860ba8df48cca3253da4f02fd2d42d856ce80 (2012-12-10))
Diffstat (limited to 'open_issues/code_analysis.mdwn')
| -rw-r--r-- | open_issues/code_analysis.mdwn | 13 |
1 files changed, 11 insertions, 2 deletions
diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn index b3908243..8c604e3f 100644 --- a/open_issues/code_analysis.mdwn +++ b/open_issues/code_analysis.mdwn @@ -137,11 +137,20 @@ 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`) + * GCC's AddressSanitizer, a memory error detector (ASan; + `-fsanitize=address`) [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. + GNU Tools Cauldron 2012. <http://code.google.com/p/address-sanitizer/>. + + Not yet [[ported to the Hurd|community/gsoc/project_ideas/gcc_asan]]. + + * GCC's ThreadSanitizer, a data race detector (TSan; `-fsanitize=thread`) + + <http://code.google.com/p/data-race-test/wiki/ThreadSanitizer> + + Not yet [[ported to the Hurd|community/gsoc/project_ideas/gcc_asan]]. * Input fuzzing |