similar to: [LLVMdev] About Address San...

Hi John and All, Thank you for the your inputs,we tried running Safecode with Liblto on our code base few weeks back,I'm very sorry to say this that we feel that safecode is not so stable and output is not so informative ,Please correct us if i'm wrong here. Thanks Again. ~Umesh On May 25, 2012 7:54 PM, "John Criswell" <criswell at illinois.edu> wrote: > On

On 5/25/12 6:57 AM, Umesh Kalappa wrote: > Hi All , > > I'm not sure the question is relevant to the forum,My apologies if not > > We are trying to instrument our code with ASan(Clang) to find the > memory errors and we see that the application execution halts when > the Asan check finds the memory issue at the being. Which mean we need > to fix the issue then

Hi, I've seen on the LLVM's Open Projet Page [1] an idea about using LLVM to generate native code in Valgrind. For what I know, Valgrind uses libVEX to translate native instructions into a bitcode, used to add the instrumentation and then translated back to native code for execution. Valgrind and LLVM are two tools that I use nearly every day. I'm also very interested in code

Hello All, I am looking at exploring what benefits SAFECode has to offer over clang S.A and llvm's instrumentation tools like memory sanitizer and address sanitizer. I could come up with the following that are not provided in ASAN/MSAN/Clang S.A -> dangling pointer error and detection -> crashes in system libraries due to security vulnerabilities. In the process, I wanted to run the

On Mon, May 14, 2012 at 4:39 PM, John Criswell <criswell at illinois.edu>wrote: > On 5/14/12 4:32 AM, Umesh Kalappa wrote: > > Hi All , > > Was trying to build the LLVM src from > http://llvm.org/svn/llvm-project/llvm/branches/release_30 ,But unable to > build the same and clang poped up with below error . > > > First, it sounds like you're building LLVM

On 2/26/15 9:54 AM, Jyoti Rajendra Allur wrote: > Hello All, > I am looking at exploring what benefits SAFECode has to offer over clang S.A and llvm's instrumentation tools like memory sanitizer and address sanitizer. Are you looking for an off-the-shelf tool, or are you looking for approaches to use in your own tool? > I could come up with the following that are not provided in

Hello, We've just released the first version of our LLVM-based address sanity checker: AddressSanitizer (http://code.google.com/p/address-sanitizer/). The tool finds out-of-bound and use-after-free bugs (the subset of bugs detectable by Valgrind/Memcheck); it consists of a LLVM compiler plugin which performs simple code instrumentation and a malloc replacement library. The main advantage of

Thank you all for the responses, John, My Bad here you go clang version 3.2 (trunk) Target: i386-pc-linux-gnu Thread model: posix [root at localhost opensrc]# cat /etc/centos-release CentOS release 6.2 (Final) Matthieu, Thanks for the fix and let me try again with latest trunk. ~Umesh On Mon, May 14, 2012 at 10:34 PM, Matthieu Monrocq <

Hi All , Was trying to build the LLVM src from http://llvm.org/svn/llvm-project/llvm/branches/release_30 ,But unable to build the same and clang poped up with below error . llvm[1]: Compiling IntervalMap.cpp for Debug build In file included from /root/projects/safecode/llvm/lib/Support/IntervalMap.cpp:14: /root/projects/safecode/llvm/include/llvm/ADT/IntervalMap.h:1980:32: error: use

Hi Kostya, > [resurrecting an old mail thread about AddressSanitizer false positive caused by > load widening] > > Once the Attribute::AddressSafety is set by clang (a separate patch), fixing > this bug may look as simple as this: I don't get the point of an attribute. There's plenty of code out there that does wide loads like this directly (without them being created by

Hi Justin , Thank you for the confirmation and we would like to know that ,going forward the clang has the support the gcc gcov format or use the -fprofile-instr-generate -fcoverage-mapping and get ride of gcov format . We are planing to customize the clang code coverage for embedded world ,before we start tweaking the gcov / -fprofile-instr-generate code-base ,we would like to take feedback

On 02/25/2014 04:50 PM, John Criswell wrote: > > I think a more interesting idea would be to use LLVM to perform > instrumentation and then to use Valgrind to instrument third-party > libraries linked into the program. > > What I'm imagining is this: Let's say you instrument a program with > SAFECode or Asan to find memory safety errors. When you run the program >

On Tue, Jan 24, 2012 at 1:23 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Kostya, > > > [resurrecting an old mail thread about AddressSanitizer false positive > caused by > > load widening] > > > > Once the Attribute::AddressSafety is set by clang (a separate patch), > fixing > > this bug may look as simple as this: > > Hi Duncan, >

Hi Kostya, > On Tue, Jan 24, 2012 at 1:23 AM, Duncan Sands <baldrick at free.fr > <mailto:baldrick at free.fr>> wrote: > > Hi Kostya, > > > [resurrecting an old mail thread about AddressSanitizer false positive > caused by > > load widening] > > > > Once the Attribute::AddressSafety is set by clang (a separate

On 5/24/12 3:51 AM, Duncan Sands wrote: > Hi Nuno, > >> I'm implementing the alloc_size function attribute in clang. > does anyone actually use this attribute? And if they do, can it really buy > them anything? How about "implementing" it by ignoring it! Tools like ASan and SAFECode *could* use this attribute to determine the size of memory objects created by

On 5/14/12 4:32 AM, Umesh Kalappa wrote: > Hi All , > > Was trying to build the LLVM src from > http://llvm.org/svn/llvm-project/llvm/branches/release_30 ,But unable > to build the same and clang poped up with below error . First, it sounds like you're building LLVM 3.0, Poolalloc, and SAFECode with an unmodified version of clang. Is this correct? If so, which version of

Umesh Kalappa <umesh.kalappa0 at gmail.com> writes: > Hi Justin , > > Thank you for the confirmation and we would like to know that ,going > forward the clang has the support the gcc gcov format or use the > -fprofile-instr-generate -fcoverage-mapping and get ride of gcov > format . Going forward, the -fprofile-instr-generate -fcoverage-mapping (which I'll refer to as

Hi: I have been working on Valgrind [porting it to non-supported architectures] and wanted to know what you guys think of Valgrind for LLVM. I haven't thought through fully myself - so wanted to get your inputs before becoming rigid in my own opinion. Original Valgrind works on object code - translating the asm to its own IR [intermediate representation]. But for LLVM, probably putting the

On 5/24/12 5:41 AM, Duncan Sands wrote: > Hi Kostya, I'm also curious to know where Nuno is going with this, and the > details of his design. I'm worried he might be reinventing the wheel. I'm > also worried that he may be inventing a square wheel :) I believe Nuno's goal is to prevent run-time exploitation of software. Nuno, please correct me if I'm wrong. And

Hi everyone, I am having troubles but this shouldn't be hard to solve for many people here. I am beginning a runtime feature for the BoundsChecking pass and I want to replace the libc malloc&free. I followed the design of AddressSanitizer (Asan) and tried to use the INTERCEPTOR macro from the interception.h file of compiler-rt library. Here is the problem. The file I modify