#define ELF_ET_DYN_BASE (mmap_is_ia32() ? 0x000400000UL : \
> > - 0x1UL)
> > + (TASK_SIZE / 3 * 2))
> >
> > /* This yields a mask that user programs can use to figure
tend to over write the store instruction in similar manner as done
> address sanitizer.
> In that quest, I want to know what exactly does option "-fsanitize=address"
> do and is there any way I can just pass on the custom code to store
> instruction.
>
> I would rea
;> I do not see any globals that I should have initialized, is there
>>> something obvious that I am missing or binary instrumentation itself is
>>> tightly coupled with Linux so reimplementing callbacks is not enough?
>>>
>>> Thank you!
>>>
>>>
ank you!
>
> --
> 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.
> To view this disc
first thing.
> >
>
> Exactly. At Red Hat, we typically wait for a corresponding kernel fix
> to pass tests before starting on our kpatch conversion (emergency CVEs
> aside) ... that way we're usually confident with the overall changes
> before we even start our work.
>
>
> On 1. Oct 2022, at 15:15, 'Dmitry Vyukov' via address-sanitizer
> wrote:
>
> On Sat, 1 Oct 2022 at 14:25, 'Koschel, J. (Jakob)' via
> address-sanitizer wrote:
>>
>> Hey,
>>
>> it was worth a shot, after Dmitry suggested to try here ;)
>> R
On Sat, 1 Oct 2022 at 14:25, 'Koschel, J. (Jakob)' via
address-sanitizer wrote:
>
> Hey,
>
> it was worth a shot, after Dmitry suggested to try here ;)
> Regardless thanks for your reply, I guess I'll have to wait a bit more.
Just in case: you considered using qemu, right?
>
ely, we are not aware of any publicly available device with usable
> MTE.
> Please pester your hardware suppliers directly, or wait :)
>
> --kcc
>
>
>
> On Thu, Sep 29, 2022 at 3:08 PM 'Jakob K.' via address-sanitizer
> wrote:
> Hi all,
>
> I'm
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/address-sanitizer/01cba890-
(skvbc_replica+0xdd1e7a)
> > #20 (skvbc_replica+0xdd2d5a)
> > #21 (libc.so.6+0x21bf6)
> >
> > Thread T73 (tid=739, running) created by main thread at:
> > #0 (skvbc_replica+0xd4019b)
> > #1 (libstdc++.so.6+0xbd994)
> > #2 (skv
options.cpp (75 of 1460)
>> > PASS: AddressSanitizer-arm-android :: TestCases/Linux/clone_test.cpp (76
>> > of 1460)
>> > PASS: AddressSanitizer-arm-android ::
>> > TestCases/Linux/new_delete_mismatch_global.cpp (77 of 1460)
>> > PASS: AddressSanitizer-arm
ressSanitizer-arm-android ::
> TestCases/Linux/printf-fortify-1.c (82 of 1460)
> > UNSUPPORTED: AddressSanitizer-arm-android ::
> TestCases/Linux/printf-fortify-2.c (83 of 1460)
> > UNSUPPORTED: AddressSanitizer-arm-android ::
> TestCases/Linux/printf-fortify-3.c (84 of 1460)
x/pthread_create_from_constructor.cpp (87 of 1460)
> PASS: AddressSanitizer-arm-android :: TestCases/Linux/clang_gcc_abi.cpp (88
> of 1460)
> PASS: AddressSanitizer-arm-android ::
> TestCases/Linux/new_delete_mismatch_stack.cpp (89 of 1460)
> XFAIL: AddressSanitizer-arm-android :: TestCase
On Tue, Apr 13, 2021 at 11:55 AM Wei Chen wrote:
>
> Hi all,
>
> I'm recently learning Address Sanitizer code and learned that the runtime
> library is designed to replace the glibc malloc/free with our customized ones
> so that we can insert red zone before and after th
t;> * Leak detection is done when a program exits, which audioflinger never
>> does. There is an API to force a leak check at runtime.
>>
>>
>> On Mon, Feb 8, 2021 at 10:05 PM varsha vanga
>> wrote:
>>
>>>
>>> Hi,
>>> I am trying to u
wrote:
>
> Hi,
> I am trying to use the address sanitizer tool in Android AOSP -(Android
> 10.)
> I am trying to check the possible memory leaks in AudioFlinger.
>
> I have added the foll. code in Android.bp file
> (frameworks/av/services/audioflinger/Android.bp)
>
m
--
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.
To view this discussion on the web visit
h
>>> ==3933371==Installed the sigaction for signal 7
>>> ==3933371==Installed the sigaction for signal 8
>>> ==3933371==SetCurrentThread: 0x77576000 for thread 0x771b1bc0
>>> ==3933371==T0: stack [0x7f7ff000,0x7ffff000) size 0x80;
>&g
t;>>0x5578cbd5 <+181>:mov$0x1,%ebx
>>>...
>>>
>>> (gdb) info registers
>>> rax0x5578cb20 0x5578cb20
>>> rbx0x0 0x0
>>> rcx0x7fffd
fddc0
> r8 0x0 0x0
> r9 0x1 0x1
> r100x77438b0f 0x77438b0f
> r110x5578e5e0 0x5578e5e0
> r120x20 0x20
> r130x200x20
> r1
ank you,
> Rodrigo
>
>
> --
> 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
; looking at all fixes).
> >
> > I see several reasonable next steps:
> > 1. Add a test with an extremely large function name in a report
> > (should be doable with some C++ recursive template magic). Wonder how
> > compilers handle function name >16K
> > Ju
e opinion in this regard.
>
> Thanks,
> Namit Gupta
>
>
>
>
>
>
--
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
t
by both LSAN and KMEMLEAK looks much
more simple and robust to me. I can imagine a compiler providing some
aid for that, like register/memory slot lifetime markers, some type
info, but all of that only fights false negatives, so I would consider
it as an optional addition only.
--
You received th
ome insight into what happens.
--
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.
To view this discussion on the w
u can now land this yourself, right?
>
>
> CHANGES SINCE LAST ACTION
> https://reviews.llvm.org/D78111/new/
>
> https://reviews.llvm.org/D78111
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To
ted source code?
>
If you can show that this thing that is being freed has been allocated with
ASan's malloc, then certainly.
> Zach
>
> On Thu, Mar 26, 2020 at 3:39 PM 'Evgenii Stepanov' via address-sanitizer <
> address-sanitizer@googlegroups.com> wrote:
>
>> This might h
> (/lan/sig/cm/cds/19.00MainQt_asan/19.00.0321/tools.lnx86/bin/hyb_engd.exe+0x9c5c97c)
>> #7 0x3064a1ecef in __libc_start_main (/lib64/libc.so.6+0x3064a1ecef)
>> #8 0x413d54
>> (/lan/sig/cm/cds/19.00MainQt_asan/19.00.0321/tools.lnx86/bin/hyb_engd.exe+0x413d54)
>>
>> Add
> (/lan/sig/cm/cds/19.00MainQt_asan/19.00.0321/tools.lnx86/bin/hyb_engd.exe+0x413d54)
>
> AddressSanitizer can not provide additional info.
> SUMMARY: AddressSanitizer: SEGV (/lib64/libc.so.6+0x3064a78d26) in
> _int_free
> ==47276==ABORTING
>
> Thanks,
> Zach
>
> --
>
ld be useful:
>> >
>> > enum {
>> > IS_INT,
>> > IS_FLOAT
>> > };
>> > struct foo {
>> > int type;
>> > union { int i; float f };
>> > };
>> >
>> > struct foo* create_int_foo(int i) {
&g
Thanks. That explains some of the 'weirdness' that I've been seeing.
David
On Friday, May 31, 2019 at 6:53:13 PM UTC-7, kcc wrote:
>
> The env overrides __asan_default_options.
>
> --kcc
>
> On Fri, May 31, 2019 at 1:03 PM 'David Barto' via address-san
ASAN_OPTIONS from the environment
__asan_default_options from the program it self?
Does one override the other, or can __asan_default_options enhance/extend the
environment variable?
David
--
You received this message because you are subscribed to the Google Groups
"address-sani
.
>
> Is this still current?
>
> Thanks!
>
> --
> 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+unsu
gt; leaf1> 27 (1792): total: 128 K allocs: 36 remains: 36
> leaf1> 28 (2048): total: 128 K allocs: 32 remains: 32
> leaf1> 29 (2560): total: 128 K allocs: 50 remains: 50
> leaf1> 30 (3072): total: 128 K allocs: 21 remains: 21
> leaf1> 31 (3584): total: 128
.g. a breakpoint on error,
> or transfer data to a PC for calculations (but what would be the required
> bandwidth ?) but that would require developing a dedicated GUI/app.
>
>
>
> Any advice ?
>
>
>
> Thomas.
>
> --
> You received this message because you are s
ptor_strlen.part.24 () from
> /lib64/libasan.so.
>
> --
> 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...
; I got the libasan_intermediates for host, but not for target, even the
> makefile mentions that these are generated for host.
>
> Can anyone please suggest me how to build the asan for target. Thanks in
> advance.
>
> Thanks,
> Harinath
>
> --
> You received this message becaus
17440 abort ~/FOT/igraph-asan/install/lib/igraph.harness.out
> ```
>
> However when `detect_stack_use_after_return=1`, there is no crash report at
> all.
>
> I will debug with the input to see the exact root cause of the crash; and if
> required, I can
/logs.txt";
> }
>
> Any idea?
extern "C"?
--
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://groups.google.com/d/optout.
eeded_size > kMaxAllowedMallocSize) {
> Report("WARNING: AddressSanitizer failed to allocate %p bytes\n",
>
> How is the kMaxAllowedMallocSize decided?
>
> Thanks.
> Xingyan
>
>
>
> --
> You received this message because you are subscribed to the Google Grou
hy this is occuring; 2)
> and how to properly write the code to make the error go away. (Note: my
> motivation for the alignas attributes is to prevent false sharing between r
> and w as this class is used by concurrent threads.)
>
> --
> You received this message because you are subsc
Hi all,
>>
>> We are running a few experiments to try to predict the performance
>> slowdown of Address Sanitizer. Our hypothesis is that an executable with
>> more memory accesses would take longer than one with fewer. We tried to
>> correlate the number of loads/sto
alekseys and I have been working on this offline, will update as soon as we
figure this out. Thanks!
On Monday, March 26, 2018 at 4:58:25 PM UTC-7, kcc wrote:
>
> +alekseys, who has been touching this code recently.
>
> On Mon, Mar 26, 2018 at 12:24 PM, isarkisov via addre
long, unsigned char
const&) external/libcxx/include/vector:1099
--
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...@g
m userspace will be reported as UNKNOWN.
>>
>> Is this likely to cause a problem?
>
> I guess this shouldn't be a bid deal.
> AFAICS compiler-rt uses this information only in diagnostic message.
+address-sanitizer mailing list
Hi,
These diagnostic messages are then parsed and analyzed,
g) struct file_operations->ioctl() ==> kernel_driver_ioctl()
> --> I have to find more condition..
>2), 3) are same to "For linux kernel"
>==> Output : Minimal sanitized kernel driver.
>
>** User-supplied list can be an easiest way as I think.
This looks too complex to be practical.
--
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://groups.google.com/d/optout.
ant o extract this list of functions? Or you mean that
user supplies the list?
--
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://groups.google.com/d/optout.
n the
> ASan side.
>
> On Thu, Oct 26, 2017 at 7:59 AM, 'Dmitry Vyukov' via address-sanitizer
> <address-sanitizer@googlegroups.com> wrote:
>> Hi,
>>
>> I am missing some context.
>> How can this be reproduced? What is the user-space program? Is it
>>
t;> > still running into issues. It appears that 32 bit processes are having an
>> > issue.
>> > Logcat attached.
>> > >
>> > > Have you seen this issue yet? The only solution we have so far is to do a
>> > complete revert of above mentioned changes.
&g
r is it merely
> response to actual reads and writes?
>
> Thank you,
> Rick C. Hodgin
>
> --
> 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, sen
com> wrote:
> On Thu, Oct 19, 2017 at 10:56 PM, <chett...@gmail.com> wrote:
> > Hi Martin,
> > I am having the same issue too, it seems to be a real issue in the
> address
> > sanitizer: https://github.com/apache/trafficserver/issues/1498.
> >
> > In
On Thu, Oct 19, 2017 at 10:56 PM, <chett...@gmail.com> wrote:
> Hi Martin,
> I am having the same issue too, it seems to be a real issue in the address
> sanitizer: https://github.com/apache/trafficserver/issues/1498.
>
> In my case I am running a C++ component on RHEL 6
LSan is not enabled on Android, see
https://github.com/google/sanitizers/issues/379
It's kind of on our TODO list, but I can not say when we might finally
get to it.
On Wed, Oct 4, 2017 at 2:48 PM, 'Primiano Tucci' via address-sanitizer
<address-sanitizer@googlegroups.com> wrote:
> H
test.o
obj/buildtools/googletest/googletest/src/gtest.gtest-all.o
obj/buildtools/googletest/googletest/src/gtest_main.gtest_main.o -llog
-lgcc -lc++_static -lc++abi -landroid_support -o sanitizers_unittests
--
You received this message because you are subscribed to the Google Groups
"add
r::Fuzzer::RunOne(unsigned char const*,
>>> unsigned long, bool, fuzzer::InputInfo*)
>>> (decode_fuzz_test:x86_64+0x1000fd553)
>>> #19 0x10f3ff200 in fuzzer::Fuzzer::MutateAndTestOne()
>>> (decode_fuzz_test:x86_64+0x100104200)
>>> #20 0x10f3ffac2 in fuzzer::Fuzzer::Loop
>repair.pData = NULL;
>
> }
>
> it = m_packets.erase(it);
>
> } else {
>
> ++it;
>
> }
>
> }
>
>
> Thanks
>
>
> --
> You received this message because you are subscribed to the Google Grou
ould require
> compiler instrumentation in addition to linking with the special LSAN
> library.
>
> Thanks,
> -Eric Feng
>
> --
> You received this message because you are subscribed to the Google Groups
> "address-sanitizer" group.
> To unsubscribe from thi
s e.g. char arrays are sometimes used as opaque storage for
compound types.
Do you have any evidence how big is the memory overhead caused by
redzones in this case?
> -Y
>
> --
> You received this message because you are subscribed to the Google Groups
> "address-sanitizer&qu
>>>
>>> On 21 Jun 2017, at 04:11, Aayushi Agrawal <aayushigr...@gmail.com>
>>> wrote:
>>>
>>> Hello
>>>
>>> I used " -fsanitise=address " as one of the option for compiling my
>>> program with clang.
>>> Bu
On Fri, Jun 9, 2017 at 4:26 PM, hariri via address-sanitizer
<address-sanitizer@googlegroups.com> wrote:
> Thanks for your reply Evgeniy.
>
>> It could be possible
> to hack something, but it does not sound easy
>
> Could you please give me some pointers into what
> me how one would tie them together.
>
>
> On Fri, Jun 9, 2017 at 8:52 AM, hariri via address-sanitizer
> <address-...@googlegroups.com > wrote:
> > Hi,
> >
> > I am trying to use the dataflow sanitizer with the address sanitizer,
> but
> >
address-sanitizer
<address-sanitizer@googlegroups.com> wrote:
> Hi,
>
> I am trying to use the dataflow sanitizer with the address sanitizer, but
> they clash together giving me a long sequence of errors due to multiple
> definitions in both sanitizers:
>
> clang-llvm/
- Eyasu Getahun Chekole
> Cc: k...@google.com; bruen...@google.com; gli...@google.com; address-sanitizer
> Subject: Re: Looking for source code of ASan
>
> On Thu, May 4, 2017 at 5:11 PM, PhD - Eyasu Getahun Chekole
> <eyasu_chek...@mymail.sutd.edu.sg> wrote:
>> Dear all,
emory and libc issues.
>>
>> It would be quite valuable for me to be able to run ASan on apps on
>> non-rooted phones (even if I could only get a subset of checks to work), so
>> I'd be willing to put in a fair amount of work to make it happen, if it's
>> the sort o
ncis
>
> --
> 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 mo
t
> with clang. I couldn't find a pointer where to get the source code to do
> that. Could you please point me where to get it?
Hi Eyasu,
The source code is in gcc already (libsanitizer/asan), just build gcc.
--
You received this message because you are subscribed to the Google Groups
&
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
] = 70;
> g[atoi(argv[1])] = 'c';
>
> }
>
> If I compile it with clang , address sanitizer and no other flags used then
> for input as "101" it gives ASAN buffer overflow message but input as "200"
> does not show any buffer overflow why ?
>
>
> Aayushi
; Currently mapping a mult-TB range doesn't work in OpenBSD. But I
> think it could be made to work if most of that range will be mapped
> with PROT_NONE.
It needs to be mapped with PROT_READ|PROT_WRITE and MAP_NORESERVE. We
don't have code that later would detect which parts of t
On Thu, Apr 20, 2017 at 12:00 PM, Yuri Gribov <tetra2...@gmail.com> wrote:
> On Thu, Apr 20, 2017 at 10:53 AM, 'Dmitry Vyukov' via
> address-sanitizer <address-sanitizer@googlegroups.com> wrote:
>> On Thu, Apr 20, 2017 at 11:50 AM, Yuri Gribov <tetra2...@gmail.com> w
On Thu, Apr 20, 2017 at 11:50 AM, Yuri Gribov <tetra2...@gmail.com> wrote:
> On Thu, Apr 20, 2017 at 10:20 AM, 'Dmitry Vyukov' via
> address-sanitizer <address-sanitizer@googlegroups.com> wrote:
>> On Thu, Apr 20, 2017 at 11:11 AM, evgeny777 <evgeny.levi...@g
vial change would
>> be to add 1 to PCs pointing to faulting instruction. Then
>> GetPreviousInstructionPc will offset this and we get correct debug
>> info. However, then we will print incorrect PC in report. So a proper
>> fix would be to augment all stack traces with a flag say
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://groups.google.com/d/optout.
u anyway!
>
> --
> 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 m
\
>(s8)s)) {
> \
> if (__asan_test_only_reported_buggy_pointer) {
> \
> *__asan_test_only_reported_buggy_pointer = addr;
> \
> } else {
> \
> GET_CALLER_PC_BP_SP;
> \
> ReportGenericError(pc, bp, sp, addr, is_write, size, exp_arg,
pport my firmware? Any suggestion is welcomed.
>
>
> Thanks
> Steven Shi
>
> --
> 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
oogle/sanitizers/wiki/AddressSanitizerHowToBuild
on how to pass these configs.
--
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://groups.google.com/d/optout.
l redzone: f4
> Stack after return:f5
> Stack use after scope: f8
> Global redzone:f9
> Global init order: f6
> Poisoned by user: f7
> ASan internal: fe
> ==6211== ABORTING
>
>
>
> Consider this as my log..how should I analyse
being reported by ASAN in GCC?
>
> Though I use verbosity where exactly should I look for is not clear...So
> can you please give me some insights on how to analyse?
>
> --
> You received this message because you are subscribed to the Google Groups
> "address-sanitizer&q
p 16, 2016 at 1:30 PM, Karthigaasri Thirunavukkarasu
<karthigaasri...@gmail.com> wrote:
> As you say it is executable file...I want to to know how to track it with
> ASAN?
>
> --
> You received this message because you are subscribed to the Google Groups
> "address-
.o image,I am wondering where can I find the error log
> generated by the address sanitizer tool.
>
> Is it because I missed something or is it because we kill the image once we
> are done?
>
> Can you help me with this?
>
> --
> You received this message because you are
On Tue, Aug 30, 2016 at 8:42 AM, WookHyun Han <wookhyun...@gmail.com> wrote:
> I'm looking address sanitizer instrumentation and found that UseCalls is
> enabled when CompileKernel is enabled
>
> When UseCalls is enabled, instrumentation inserts function calls which check
&g
get older builds would it
> be possible that there's a directory that contains links to only the
> latest two or three versions of each build?
>
> --
> Hanno Böck
> https://hboeck.de/
>
> mail/jabber: ha...@hboeck.de
> GPG: BBB51E42
>
> --
> You received this m
for the
UBSan.
Greetings, and thanks,
Ilya
Am Montag, 9. Mai 2016 11:07:49 UTC+2 schrieb Yuri Gribov:
>
> On Mon, May 9, 2016 at 10:35 AM, 'Ilya' via address-sanitizer
> <address-...@googlegroups.com > wrote:
> >
> >> Worst case you could w
ot;.
--
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://groups.google.com/d/optout.
ns.
This understanding however might be crucial for
me to utilize it to suppress the lasting ubs.
The slowdown could be acceptable, so I'm not worrying about that currently.
Thanks, Ilya
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer&q
u 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://groups.google.com/d/optout.
an add -lpthread whenever you add -fsanitize=address.
--
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://groups.google.com/d/optout.
gt;
> What is the command line equivalent of 'check_initialization_order=true'?
>
> Thanks in advance.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "address-sanitizer" group.
> To unsubscribe from this group and stop rece
t would avoid introducing another flag. Not sure if that
> breaks any other use case.
>
> --
> Hanno Böck
> http://hboeck.de/
>
> mail/jabber: ha...@hboeck.de
> GPG: BBB51E42
>
> --
> You received this message because you are subscribed to the Google Groups
> "addres
Comment #1 on issue 407 by zhouweig...@gmail.com: gcc-asan doesn't work on
android/arm32
https://code.google.com/p/address-sanitizer/issues/detail?id=407
I submitted the same bugs on gcc's bugzilla system. the following is the
URL.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67286
I
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 407 by zhouweig...@gmail.com: gcc-asan doesn't work on
android/arm32
https://code.google.com/p/address-sanitizer/issues/detail?id=407
What steps will reproduce the problem?
1.built the testcase invalid-free.cc with cross
Updates:
Labels: ProjectAddressSanitizer
Comment #3 on issue 403 by ramosian.gli...@gmail.com: Enable LSAN support
for 32bit architecture
https://code.google.com/p/address-sanitizer/issues/detail?id=403
(No comment was entered for this change.)
--
You received this message because
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 404 by dvyu...@google.com: support relative paths in backlist
files
https://code.google.com/p/address-sanitizer/issues/detail?id=404
Paths in backlist files must much paths passed to compiler by build system
Wasn't sure where I need to file the issue due to c.g.c closure. Now filed:
https://code.google.com/p/address-sanitizer/issues/detail?id=404
On Thu, Aug 13, 2015 at 3:03 PM, Ilya Mirsky ilya.mir...@gmail.com wrote:
I agree, it would be best.
Is there a ticket I could follow?
On Wed, Aug 12
Comment #2 on issue 403 by tetra2...@gmail.com: Enable LSAN support for
32bit architecture
https://code.google.com/p/address-sanitizer/issues/detail?id=403
As this keeps popping up, perhaps add a descriptive message to #error in
lsan header?
--
You received this message because
+address-sanitizer
Thanks for the report!
I guess it is the same for asan as well.
I think we need to promote usage of relative paths (absolute paths are
not portable between machines), and then match then as suffix of
compiled source files.
On Wed, Aug 12, 2015 at 1:24 PM, Ilya Mirsky
Comment #1 on issue 403 by konstant...@gmail.com: Enable LSAN support for
32bit architecture
https://code.google.com/p/address-sanitizer/issues/detail?id=403
This has come up before, including the bug you mentioned above,
and it is problematic for the reasons you mostly explained. :)
We
Updates:
Labels: ProjectAddressSanitizer
Comment by ramosian.gli...@gmail.com:
(No comment was entered for this change.)
Affected issues:
issue 7: No redzones for weak symbols
http://code.google.com/p/address-sanitizer/issues/detail?id=7
issue 12: need to instrument thread
Updates:
Labels: ProjectAddressSanitizer
Comment by ramosian.gli...@gmail.com:
Adding Project:AddressSanitizer as part of GitHub migration.
Affected issues:
issue 115: Trivial program crashes with dynamic runtime on Mac
http://code.google.com/p/address-sanitizer/issues/detail?id
1 - 100 of 632 matches
Mail list logo
