search for: drmemory

...This gives us much better register allocation (function-wide instead of local), possible compiler optimizations (static analysis can prove that some accesses always read initialized memory), and a fast start-up. Our preliminary measurements show 3x-4x slowdown; compare it to Memchecks's 20x and DrMemory's 10x. (See http://groups.csail.mit.edu/commit/papers/2011/bruening-cgo11-drmemory.pdf for those numbers). But this brings the major issue as well: msan needs to see all program events, including system calls and reads/writes in system libraries, so we either need to compile *everything* with m...

...ter allocation (function-wide instead of > local), > possible compiler optimizations (static analysis can prove that some > accesses always read initialized memory), > and a fast start-up. > Our preliminary measurements show 3x-4x slowdown; compare it to > Memchecks's 20x and DrMemory's 10x. > (See > http://groups.csail.mit.edu/commit/papers/2011/bruening-cgo11-drmemory.pdf for > those numbers). > But this brings the major issue as well: msan needs to see all program > events, including system calls and reads/writes in system libraries, > so we either need...

...-wide instead of >> local), >> possible compiler optimizations (static analysis can prove that some >> accesses always read initialized memory), >> and a fast start-up. >> Our preliminary measurements show 3x-4x slowdown; compare it to >> Memchecks's 20x and DrMemory's 10x. >> (See >> http://groups.csail.mit.edu/commit/papers/2011/bruening-cgo11-drmemory.pdf for >> those numbers). >> But this brings the major issue as well: msan needs to see all program >> events, including system calls and reads/writes in system libraries, &gt...

...n regular C/C++ code (usually, in codecs or compression code). Strictly speaking -- all these cases are bugs, according to either C or C++ standard, and asan does not impose more restrictions than the standard. Note, that the hacks like these hurt not only address safety checkers like asan/memcheck/drmemory/SAFEcode/etc, but also race detectors like tsan/helgrind/drd/etc. We still have lots of code with these intentional OOB accesses and we want to test it. In most cases I've met so far, the developers decided to actually fix the bugs according to the C++ standard and require the memory allocatio...

...ally, in codecs or > compression code). > Strictly speaking -- all these cases are bugs, according to either C or C++ > standard, and asan does not impose more restrictions than the standard. > Note, that the hacks like these hurt not only address safety checkers like > asan/memcheck/drmemory/SAFEcode/etc, but also race detectors like > tsan/helgrind/drd/etc. > > We still have lots of code with these intentional OOB accesses and we want to > test it. > In most cases I've met so far, the developers decided to actually fix the bugs > according to the C++ standard and...

Dear All, We have a new release of Clang with SAFECode technology for detecting memory safety errors. Memory safety checking (SAFECode for short) can be turned on with a single command line switch to clang/clang++. The SAFECode techniques do not change the behavior of the clang/clang++ compilers in any way when the switch is turned off, so this can be used as a drop-in replacement for

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

...ompression code). >> Strictly speaking -- all these cases are bugs, according to either C or >> C++ >> standard, and asan does not impose more restrictions than the standard. >> Note, that the hacks like these hurt not only address safety checkers like >> asan/memcheck/drmemory/**SAFEcode/etc, but also race detectors like >> tsan/helgrind/drd/etc. >> >> We still have lots of code with these intentional OOB accesses and we >> want to >> test it. >> In most cases I've met so far, the developers decided to actually fix the >> bug...

Hi, I am new to using wine. I wanted to run our office's tax preparation program (Drake). Using wine, I installed a workstation version of Drake by running a program off the server, as has been done on the windoze machines here. I can get the program to start (the console shows "fixme:wininet: InternetGetConnectedState always returning LAN connection", but I understand that this is