Comment #4 on issue 313 by [email protected]: [libsanitizer]
Fallback to llvm-symbolizer in PATH
http://code.google.com/p/address-sanitizer/issues/detail?id=313
I'm talking about the following scenario.
Most often Chrome developers run their binaries from src/, so we may want
to compile the default external_symbolizer_path into the binary.
However if the working dir is different the devs won't be able to get
symbolized output despite they may have llvm-symbolizer in $PATH. In this
case we may want to check for llvm-symbolizer in $PATH if it isn't in
external_symbolizer_path.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
