Users often have path escaping bugs in their ASan options. They do
things like this
ASAN_OPTIONS=foo=1:bar=0:symbolizer_path=%s
... where %s is an absolute path. They may have project rules that
require paths to not contain spaces, so they get away with this on
Linux. Then they come to Windows, and the substituted options look like:
symbolizer_path=C:/path/to/llvm-symbolizer.exe
This doesn't work because we have chosen colon to be an option
separator.
Many users have hit this, it affects the Go race detector, and it
affects Chromium Windows ASan usage. Try to make their life a little
easier by not treating colon before slash as a flag separator.
All these variables are mapped to the same C++ members. So not sure if it's worth it but what if we generalize to:
":" is separateor IFF it's followed by "[a-zA_Z0-9_]+="