similar to: [LLVMdev] More ARM asan failures - Line number

On 7 October 2014 20:55, Evgeniy Stepanov <eugenis at google.com> wrote: > Can you elaborate on this? Does it ever clean those lines? These > numbers are correct on multiple other platforms. I wonder if it's some > codegen peculiarity that leads to this off-by-one mistake? Can you go > down to the individual compile/run invocation and verify that line > numbers match (or

In order to isolate the problem I am now running on a machine whose only installation of gcc/g++ is gcc44, g++44 For this installation I am getting the following error: COMPILE: clang_linux/asan-i386/i386: /gpfs/haifa-p4/00/pincette/sitvanit/LLVM/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc /.../sitvanit/LLVM/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:19:10: fatal error:

Ok, I got. You should install libstdc++44-devel, too. Please try to install gcc44-c++ and libstdc++44-devel. Note: gcc44-c++ depends on gcc44, but gcc44-c++ and libstdc++44-devel are independent each other, at least on my host, CentOS5. ...Takumi 2012/7/15 Sitvanit Ruah <RUAH at il.ibm.com>: > In order to isolate the problem I am now running on a machine whose only > installation

I get leaks from a system library: ==16272==ERROR: LeakSanitizer: detected memory leaks Direct leak of 148 byte(s) in 2 object(s) allocated from: #0 0x4a3172 in __interceptor_malloc .../build/../projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40:3 #1 0x7f575d8df1fe in wcsdup (/lib64/libedit.so.0+0x1c1fe) I don't think I can fix this... ;] -Chandler -------------- next part

Hello, when I build llvm from git source, some errors occured. 80>asan_new_delete.obj : error LNK2019: unresolved external symbol "void * __cdecl MemalignFromLocalPool(unsigned __int64,unsigned __int64)" (?MemalignFromLocalPool@@YAPEAX_K0 at Z)， "void * __cdecl operator new(unsigned __int64)" (??2 at YAPEAX_K@Z)

I have ported ASan in LLVM to Myriad RTEMS, and I would like to upstream the port. Below is the design doc. Feedback welcome. https://docs.google.com/document/d/1oxmk0xUojybDaQDAuTEVpHVMi5xQX74cJPyMJbaSaRM The port is expected to work with modified versions of RTEMS and newlib. I have a git repo with changes to those projects, that I can make available if there is interest. Here is the patch

I assume you are using Visual Studio as your build tool? The LLVM project set turns into a bunch of Visual Studio project files, and my experience has been that they do not always coordinate correctly. Often just running the build again will solve a problem like this. I'm not really familiar with the sanitizers so I don't have any ideas about the specific error, if re-running the build

Hi Walter, I've done a first quick scan. Overall looks reasonable, but I'd like to try reducing the number of newly introduced platform-specific ifs. Vitaly, please also take a look (once my initial comments are addressed). One outstanding issue is your problem with initialization vs checking, which requires you to insert so many ifs. Is there any chance you can avoid this? If you

I used to build llvm/clang on windows a lot, and never had any issues. But I never built asan on windows, maybe asan just doesn't build on windows? On Tue, Mar 12, 2019 at 7:14 PM mirchd via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I am using Visual Studio 2017, > I re-running cmake and rebuild the project but it still has the unresolved link error. > > thanks

The asan bootstrap bot is unhappy with lld. Rui, os someone, please take a look. http://lab.llvm.org:8011/builders/sanitizer-x86_64- linux-bootstrap/builds/138/steps/check-lld%20asan/logs/stdio ==26011==ERROR: LeakSanitizer: detected memory leaks Direct leak of 184 byte(s) in 1 object(s) allocated from: #0 0x72fab0 in operator new(unsigned long)

On Thu, Nov 12, 2015 at 8:42 PM, Kostya Serebryany <kcc at google.com> wrote: > 2 questions: > - Do you see this with the fresh llvm trunk? > - Can you prepare a minimized example? Pretty recent, I updated a couple days ago. I tried to minimize the attached but at the same time I didn't want to lose too many unions and casts in case it didn't trigger any more. $ clang

Hey, I work on fuchsia symbolizer stuff. I don't know if you guys already have an external symbolizer but I'm working on making one right now and I plan on making one backed by LLVM that can be run host-side or target-side. I'd like to contribute that back to llvm ideally. What do you guys have so far? I have a prototype in golang that just spins up an instance of llvm-symbolizer

On Mon, Nov 7, 2016 at 5:53 PM, Davide Italiano <davide at freebsd.org> wrote: > On Mon, Nov 7, 2016 at 4:43 PM, Kostya Serebryany via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> The asan bootstrap bot is unhappy with lld. >> Rui, os someone, please take a look. >> >>

Kostya, all, I'm trying to build my project by clang 3.8rc1 with enabled asan (clang itself is address sanitized) and it fails on several files from my project (ISPC, https://github.com/ispc/ispc). I've reproduced this on MacOS and Linux. Please let me know if you need any other info. How to reproduce: 1) Build address sanitized clang 3.8rc1: cd /path-to-working-dir svn co

Hi Jake. Thanks for the info. Where can I keep up to date on the symbolizer status? Our symbolizer is provided by the Myriad vendor and integrated into its host test environment. It doesn't do much: just look for PC string patterns and symbolize them using addr2line. Thanks, Walter On Fri, May 4, 2018 at 5:36 PM Jake Ehrlich <jakehehrlich at google.com> wrote: > Hey, > I

Hi Kostya. Thanks for the quick feedback. I will work on addressing your comments. In regard to initialization checks, I can eliminate most of them by initializing the shadow memory very early, but I still need to do something in two places, __asan_handle_no_return and GetFakeStackFast. Would it be ok to have guards for those two places only? Walter On Fri, May 4, 2018 at 6:10 PM Kostya

PS: Do you actually have gcc-4.4 installed and in your path? What do the commands gcc44 -v and g++44 -v output? On 15/07/12 10:59, Duncan Sands wrote: > Hi Sitvanit, > >> I tried >> >> CC=gcc44 CXX=g++44 ../llvm/configure >> >> and got >> >> CC=gcc44: Command not found >> >> So the syntax is indeed as wriiten in the help. >

Hi Sitvanit, > I tried > > CC=gcc44 CXX=g++44 ../llvm/configure > > and got > > CC=gcc44: Command not found > > So the syntax is indeed as wriiten in the help. actually, no, this just means that you are using a shell that doesn't support this syntax. What shell are you using? Try export CC=gcc44 export CXX=g++44 ../llvm/configure Ciao, Duncan. >

I'm struggling to explain an ASAN report I'm now getting that I didn't get previously on the same code. In fact the report only happens with -O2 and not when I remove the -O flags which makes it hard to debug and makes me suspect it's dependent on exactly which instructions the code generation decides to access the bytes involved. Afaict the C code shouldn't be accessing the

First off, thanks -- this is a pretty great library and it feels like I'm learning a lot. I'm getting some more experience with libfuzzer and finding that I have a couple of questions: - How does libfuzzer decide to write a new test file? What distinguishes this one from all the other cases for which new test inputs were not written? Must be something about the path taken through the