Displaying 3 results from an estimated 3 matches for "testwsmanrequestencoder".
2013 Jan 08
1
[LLVMdev] Will LLVM be suitable for developing valgrind like tools
...specified in the link
I got following lines on RHEL 6.3
clang 3.2
==10474== ERROR: AddressSanitizer: heap-use-after-free on address
0x7fb3eb2c6b90 at pc 0x415394 bp 0x7fff49175eb0 sp 0x7fff49175ea8
READ of size 4 at 0x7fb3eb2c6b90 thread T0
#0 0x415393
(/home/deleisha/CodeSpace/pegasus/pkg/bin/TestWSMANRequestEncoder+0x415393)
#1 0x41619a
(/home/deleisha/CodeSpace/pegasus/pkg/bin/TestWSMANRequestEncoder+0x41619a)
#2 0x3e8003614c (/lib64/libc-2.12.so+0x3614c)
0x7fb3eb2c6b90 is located 16 bytes inside of 64-byte region
[0x7fb3eb2c6b80,0x7fb3eb2c6bc0)
freed by thread T0 here:
#0 0x4382f2
(/home/deleish...
2013 Jan 07
0
[LLVMdev] Will LLVM be suitable for developing valgrind like tools
Did you checkout compiler-rt?
This page has detailed info on building asan:
http://code.google.com/p/address-sanitizer/wiki/HowToBuild?tm=4
--kcc
On Mon, Jan 7, 2013 at 9:38 PM, Devchandra L Meetei <dlmeetei at gmail.com>wrote:
> Thanks All
> In fact, to answer Pete, I was trying to do as much as possible like
> valgrind including as much as possible, which includes all tools.
2013 Jan 07
2
[LLVMdev] Will LLVM be suitable for developing valgrind like tools
Thanks All
In fact, to answer Pete, I was trying to do as much as possible like
valgrind including as much as possible, which includes all tools.
M very elated to know about ASan, given the fact that LLVM is Compile time
whereas valgrind is Dynamic, need to rethink,
Can you guys check this. build clang 3.2 but I got this linker error. Let
me also examine closely
clang++ -W -Wall