Comment #18 on issue 330 by mguse...@gmail.com: Support re-exec of
sanitized executable with preloading libasan on Linux and Android
https://code.google.com/p/address-sanitizer/issues/detail?id=330
Ping.
I still wonder about Reexec. In current design MaybeReexec part of Asan
runtime is not
In-process symbolizer sometimes makes deployment easy, as you don't need to
carry an extra library or binary. For the same reason we prefer linking
runtime library statically where possible.
AFAIK, libbacktrace is used in gcc asan only.
Another internal symbolizer can be found here:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 361 by jon34056...@gmail.com: CHECK failed (assert() tls + stack)
on Linux in 32bit threaded
https://code.google.com/p/address-sanitizer/issues/detail?id=361
What steps will reproduce the problem?
1. Build
On Thu, Dec 4, 2014 at 4:48 PM, Yury Gribov y.gri...@samsung.com wrote:
On 12/04/2014 03:47 PM, Dmitry Vyukov wrote:
size_in_bytes = -1 instrumentation is too slow to be the default in
kernel.
If we want to pursue this, I propose a different scheme.
Handle 8+ byte accesses as 1/2/4
On Thu, Dec 4, 2014 at 8:06 PM, 'Dmitry Vyukov' via address-sanitizer
address-sanitizer@googlegroups.com wrote:
You answered your own question about user space :)
Yeah, I hoped someone would rush to overpersuade me...
-Y
--
You received this message because you are subscribed to the Google
Hi,
On Wed, Dec 3, 2014 at 3:59 PM, Kuba Brecka kuba.bre...@gmail.com wrote:
Hi everyone,
I'd like to ask about the various symbolizers that are used by ASan and
sanitizer_common, and then propose some changes to get better OS X support.
If I understand correctly, the general
