s from it, send an
> email to address-sanitizer+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/address-sanitizer/390ebc47-e6a3-4744-b5fa-92f3337c3521n%40googlegroups.com.
--
Alexander Potapenko
Software Engineer
Google
eceived 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 address-...@googlegroups.com.
>> > To view this discussion o
On Thu, Dec 12, 2019 at 1:03 PM Andrea Fioraldi
wrote:
>
> Hi to all,
Hi Andrea,
> there is a way to poison bytes as read-only in the ASAN runtime?
> For instance, I have a type field in a dynamic allocated structure that is
> assigned only at creation
> and I want to mark it as read-only
A lot of things have changed since 2015.
For example, new ASan features could've been introduced that increase
the slowdown.
Maybe some previously disabled features got enabled by default. Maybe
there were changes to the runtime (e.g. the allocator), or a newly
added interceptor increased the
K allocs: 18 remains: 18
> leaf1> 32 (4096): total: 128 K allocs: 16 remains: 16
> leaf1> 33 (5120): total: 256 K allocs: 48 remains: 48
> leaf1> 35 (7168): total: 128 K allocs: 9 remains: 9
> leaf1> 36 (8192): total: 832 K allocs: 96 remains: 96
> leaf1> 37 (
ubscribed to the Google Groups
> "address-sanitizer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to address-sanitizer+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Alexander
@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
Sitz d
If you've downloaded an ASan-instrumented build of Chromium, you don't
need LLVM already - just start using the instrumented browser and look
out for the bug reports.
On Mon, Oct 9, 2017 at 5:21 PM, wrote:
> Hi,
>
> can someone enlighten me on how to use ASan with
ot; group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to address-sanitizer+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straß
This is more or less expected.
As Kuba said, there's no distinction between a check for a heap overflow or
global overflow - we just check that every memory access is valid.
On Thu, Jun 22, 2017 at 9:08 AM, Aayushi Agrawal
wrote:
> Yes I tried but its coming out to be
sue which is not handled by address sanitizer ?
>
> On 02-May-2017 5:45 pm, "'Alexander Potapenko' via address-sanitizer"
> <address-sanitizer@googlegroups.com> wrote:
>>
>> Most certainly the access to global_array[200] ends up touching a
>> valid locat
>
> --
> 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 address-sanitizer+unsubscr...@googlegroups.com.
> For more options, visit https
this?
>
> --
> 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 address-sanitizer+unsubscr...@googlegroups.com.
> For more o
May I ask you to post the actual report you want to analyze?
sent from phone
On Sep 17, 2016 9:43 AM, "Karthigaasri Thirunavukkarasu" <
karthigaasri...@gmail.com> wrote:
> Thank you again for your valuable insight...Can you help me with how to
> analyse the error that is being reported by ASAN
sanitizer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to address-sanitizer+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Ma
subscribed to the Google Groups
> "address-sanitizer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to address-sanitizer+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Alexander
Hello there,
You can refer to https://github.com/ramosian-glider/clang-kernel-build
for the instructions on how to build the upstream kernel with Clang.
HTH,
Alex
On Tue, Sep 13, 2016 at 1:35 PM, WookHyun Han wrote:
> Hi,
> I'm doing a research to instrument Asan and
)
- 132 global names
The 1052 source locations contained 1049 unique line/column pairs and
referenced several instances of a single filename string.
We can easily save 8 bytes on each of those 1052
__asan_global_source_location structs.
On Fri, Dec 26, 2014 at 3:40 PM, Alexander Potapenko gli
are subscribed to the Google Groups
address-sanitizer group.
To unsubscribe from this group and stop receiving emails from it, send an
email to address-sanitizer+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google
On Fri, Nov 28, 2014 at 12:26 PM, wuning shi wuning@gmail.com wrote:
hello
1. can you tell me where is the memory scan in source code?(which file?
which class? which function?)
i read the most lsan source code, but i don't find that scan code : (
ScanRangeForPointers() in
Hello.
The main problem with 32-bit leak checking is that too many random 4-byte
sequences look like pointers.
In order to find live objects in the heap LSan scans the memory that's
already known to be live and looks for pointers in it. Because LSan doesn't
know anything about data types, it has
Assuming you already know how to build an application targeting the iOS
simulator, you just need to use the trunk version of Clang (not the one
shipped with Xcode) and pass -fsanitize=address when compiling and linking
the code.
There's a pretty nice writeup on using ASan with iOS simulator by
Someone did consider it, but I think it just wasn't important enough.
Doesn't the sleep_before_dying option work for you?
On Oct 29, 2014 12:24 AM, Yury Gribov y.gri...@samsung.com wrote:
Hi all,
Has anyone considered adding a flag to ASAN_OPTIONS to start gdb
automatically when
, Sep 25, 2014 at 2:16 AM, 'Alexander Potapenko' via
address-sanitizer address-sanitizer@googlegroups.com wrote:
Some time ago I've been thinking about adding a flag for each
interceptor that disables checks in that interceptor similar to
replace_intrin flag.
Using suppressions
and stop receiving emails from it, send an
email to address-sanitizer+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Moscow
--
You received this message because you are subscribed to the Google Groups
an
email to address-sanitizer+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Moscow
--
You received this message because you are subscribed to the Google Groups
address-sanitizer group.
To unsubscribe
to address-sanitizer+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Moscow
--
You received this message because you are subscribed to the Google Groups
address-sanitizer group.
To unsubscribe from this group
to the Google Groups
address-sanitizer group.
To unsubscribe from this group and stop receiving emails from it, send an
email to address-sanitizer+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Moscow
--
You
, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Moscow
--
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 address
This is an env variable ASAN_OPTIONS= allocator_may_return_null=1
On Mar 15, 2014 9:49 PM, Jeffrey Walton noloa...@gmail.com wrote:
I ==26311==WARNING: AddressSanitizer failed to allocate 0x7fff
bytes
==26311==AddressSanitizer's allocator is terminating the process
instead of
Hello there,
We've reproduced this bug with Chromium code (see
https://code.google.com/p/address-sanitizer/issues/detail?id=274)
Can you please update to Clang r203916 and verify that it's fixed?
On Tue, Feb 18, 2014 at 3:38 PM, Alexander Potapenko gli...@google.com wrote:
Thanks very much
Do you have a standalone repro?
On Mar 9, 2014 1:04 AM, address-saniti...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 272 by sabotag...@gmail.com: Attempting double-free on IOS with
SDL
I thought that some optimization cases mentioned on this page could be
handled by segregating the sanitizing code from the accesses themselves.
Can you please elaborate what do you mean by segregation here?
Is it actually treating the sanitizing code as function calls taking
the variables as
33 matches
Mail list logo