search for: dfsan

Hi all, I was trying to compile dfsan with wget. (Just enabling the dfsan feature, without actually making changes to the source code) Without dfsan, I am able to compile and run wget 1.19.5 (available at https://ftp.gnu.org/gnu/wget/wget-1.19.5.tar.gz). But when compiled with dfsan, it encountered a null pointer dereference error. Fo...

...e invocation) So I also tried adding -fPIC option at step 1 when converting .c program to .bc and still results in same error. Is there anything else I may be missing here. Thanks On Fri, Jun 2, 2017 at 9:25 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > Programs compiled with dfsan require a runtime library in order to work > correctly. You will need to link your program with "clang > -fsanitize=dataflow". > > Peter > > On Fri, Jun 2, 2017 at 12:46 AM, Archa . via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi, >> &...

...ir type in some way, I started looking at all calls to llvm::Function::takeName to see if there were any other debug info quality bugs in similar callers. One such caller is the DataFlowSanitizer, and I don't see any debug info tests for this so I'm wondering what /should/ happen here. Is DFSan+DebugInfo something that matters? I assume so. It looks like DFSan is creating wrappers (in/around DataFlowSanitizer.cpp:680-700) - when it does this, should it update the debug info for these functions? Or are these internal instrumentation functions & nothing to do with the code the user wro...

...m::Function::takeName to see if there > > were any other debug info quality bugs in similar callers. > > > > One such caller is the DataFlowSanitizer, and I don't see any debug info > > tests for this so I'm wondering what /should/ happen here. > > > > Is DFSan+DebugInfo something that matters? I assume so. > > It may be important in the future, but at the moment the dfsan runtime > library > does not make use of debug info. The debug info could still be useful for > regular debugging tasks though. > Yeah - that'd be the baseline. I...

Hi all, I have some questions about "DataFlowSanitizer" from "compiler-rt". I want to know how I can test the "DataFlowSanitizer"? Can I configure it to label only some values, i.e, the return values from specific functions? Also, how can I print these labels? Thanks, Dareen -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, Oct 7, 2014 at 2:51 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > Looks good, thanks! > > Can you write the test case, please? You probably have more experience > writing debug info tests than I do. > Sure - though how would I get the pre-dfsan .ll file to produce this behavior? I've tried compiling to a .ll file without dfsan, then feeling that .ll through opt -dfsan, and I got different output. Instead of wrapping main, it just replaced it. Is there some attribute or other thing the frontend is adding to ensure main is wrapped, rath...

...any other debug info quality bugs in similar callers. >>> > >>> > One such caller is the DataFlowSanitizer, and I don't see any debug >>> info >>> > tests for this so I'm wondering what /should/ happen here. >>> > >>> > Is DFSan+DebugInfo something that matters? I assume so. >>> >>> It may be important in the future, but at the moment the dfsan runtime >>> library >>> does not make use of debug info. The debug info could still be useful for >>> regular debugging tasks though. &g...

r247321 refactors the code so that it should build on Mac. I haven't actually tested it on Mac -- so please help me and send follow up patches if needed. check-fuzzer will still fail because some of the libFuzzer tests require dfsan. I'd use some help from someone with a Mac to modify lib/Fuzzer/test/CMakeLists.txt so that it does not run dfsan-dependent tests on Mac. Thanks, --kcc On Wed, Sep 9, 2015 at 9:41 AM, Kostya Serebryany <kcc at google.com> wrote: > > > On Wed, Sep 9, 2015 at 12:57 AM, AlexDeni...

...gt; >>> > > > >>> > One such caller is the DataFlowSanitizer, and I don't see any debug > > >>> info > > >>> > tests for this so I'm wondering what /should/ happen here. > > >>> > > > >>> > Is DFSan+DebugInfo something that matters? I assume so. > > >>> > > >>> It may be important in the future, but at the moment the dfsan > runtime > > >>> library > > >>> does not make use of debug info. The debug info could still be > useful f...

Hi there. I’m trying to use LibFuzzer on OSX and face some issues: I checked out LibFuzzer documentation[1] and managed to proceed until the final step of the first example. Now I see linker errors related to dfsan, dfsan’s documentation[2] states explicitly “DataFlowSanitizer is a work in progress, currently under development for x86_64 Linux.”. Does it mean that LibFuzzer available only on Linux platform? Can somebody confirm or refute my conclusion? [1] http://llvm.org/docs/LibFuzzer.html [2] http://clan...

FWIW see also http://lists.cs.uiuc.edu/pipermail/cfe-dev/2015-June/043301.html As far as I understand DFSan functionality isn't required for libFuzzer to work, so it should be safe to disable DFSan support on Mac. On Wed, Jul 8, 2015 at 7:45 AM, Kostya Serebryany <kcc at google.com> wrote: > +pcc , glider > > On Mon, Jul 6, 2015 at 12:59 PM, Juan Ceasar <juan.d.ceasar at gmail.com&...

...),-m32),0) SupportedArches += i386 endif @@ -74,6 +85,22 @@ Arch.lsan-x86_64 := x86_64 endif +# Build runtime libraries for x32. +ifeq ($(call contains,$(SupportedArches),x32),true) +Configs += full-x32 profile-x32 san-x32 asan-x32 tsan-x32 \ + msan-x32 ubsan-x32 ubsan_cxx-x32 dfsan-x32 lsan-x32 +Arch.full-x32 := x32 +Arch.profile-x32 := x32 +Arch.san-x32 := x32 +Arch.asan-x32 := x32 +Arch.tsan-x32 := x32 +Arch.msan-x32 := x32 +Arch.ubsan-x32 := x32 +Arch.ubsan_cxx-x32 := x32 +Arch.dfsan-x32 := x32 +Arch.lsan-x32 := x32 +endif + ifneq ($(LLVM_ANDROID_TOOLCHAIN_DIR),) Configs...

Hi all, Any one tried using DataFlowSanitizer on Linux x86_64? I tried on: 3.13.0-44-generic #73~precise1-Ubuntu SMP Wed Dec 17 00:39:15 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux It assumes wrong memory layout and remaps application code segment as shadow memory, thus causing SIGSEV (Segmentation fault). Is this know? and fix under way? -Thanks, Aravind -------------- next part

...Do they operate on IR as any other LLVM pass? Or are they integral part of the frontend itself? I couldn't spot any documentation on the internals of compiler-rt project? What happens (sequence of actions) when I pass -fsanitizer=dataflow to clang? Precisely, I intend to alter the behaviour of DFSan to suit my need. Therefore, I need to know how it gets integrated in the tool-chain. Initially, my idea was to insert the dfsan_set_label() calls to the IR and pass it to DFSan. However, I am not sure if it's designed to run on the source only, not on IR. -- Thanks & Regards, Dipanjan --...

...t a shot and see what I can do to give some patches > back. > > On Wed, Jul 8, 2015 at 9:42 AM, Alexander Potapenko <glider at google.com> > wrote: > >> FWIW see also >> http://lists.cs.uiuc.edu/pipermail/cfe-dev/2015-June/043301.html >> As far as I understand DFSan functionality isn't required for >> libFuzzer to work, so it should be safe to disable DFSan support on >> Mac. >> >> On Wed, Jul 8, 2015 at 7:45 AM, Kostya Serebryany <kcc at google.com> wrote: >> > +pcc , glider >> > >> > On Mon, Jul 6,...

Approved. On Wed, Mar 23, 2016 at 5:09 AM, Mohit Bhakkad <mohit.bhakkad at gmail.com> wrote: > Hi Peter, > > Request you to approve the merger of this patch to 3.8.1 branch: > > http://reviews.llvm.org/rL263001 > > Thanks, > Mohit > -- -- Peter -------------- next part -------------- An HTML attachment was scrubbed... URL:

I'm trying to build the example C++ file on the DFSan sanitizer page: https://clang.llvm.org/docs/DataFlowSanitizer.html However, i'ts complaining about unknown types (intptr_t, uint16_t, uint32_t, uint64_t). I got it to build after adding typedefs from stdint.h and sys/types.h to the sanitizer/common_interface_defs.h header file: typedef __intpt...

Hi, I need to be able to use a special case list file containing thousands of entries (namely, a list of libc symbols, to be used when using DFSan with an uninstrumented libc). Initially I built the symbol list like this: fun:sym1=uninstrumented fun:sym2=uninstrumented fun:sym3=uninstrumented ... fun:sym6000=uninstrumented What I found was that, despite various bits of documentation [1,2], the symbol names are matched as substrings, the ro...

...; endif > @@ -74,6 +85,22 @@ > Arch.lsan-x86_64 := x86_64 > endif > > +# Build runtime libraries for x32. > +ifeq ($(call contains,$(SupportedArches),x32),true) > +Configs += full-x32 profile-x32 san-x32 asan-x32 tsan-x32 \ > + msan-x32 ubsan-x32 ubsan_cxx-x32 dfsan-x32 lsan-x32 > +Arch.full-x32 := x32 > +Arch.profile-x32 := x32 > +Arch.san-x32 := x32 > +Arch.asan-x32 := x32 > +Arch.tsan-x32 := x32 > +Arch.msan-x32 := x32 > +Arch.ubsan-x32 := x32 > +Arch.ubsan_cxx-x32 := x32 > +Arch.dfsan-x32 := x32 > +Arch.lsan-x32 := x32 > +e...

...EARCH/llvm-git/obj/lib/clang/3.7.0/lib/linux/ > ll *.a |grep x86 | awk '{print $9}' libclang_rt.asan_cxx-x86_64.a libclang_rt.asan-preinit-x86_64.a libclang_rt.asan-x86_64.a libclang_rt.builtins-x86_64.a libclang_rt.dd-x86_64.a libclang_rt.dfsan-libc-x86_64.a libclang_rt.dfsan-x86_64.a libclang_rt.lsan-x86_64.a libclang_rt.msan-x86_64.a libclang_rt.profile-x86_64.a libclang_rt.tsan-x86_64.a libclang_rt.ubsan_cxx-x86_64.a libclang_rt.ubsan_standalone_cxx-x86_64.a libclang_rt.ubsan_stan...