similar to: Checking packages with address sanitizer

Some time ago I (and some other CRAN package maintainers) got an email from Brian Ripley (copied below) regarding compiler warnings under gcc 8.1. In my case this concerns package PropClust (https://CRAN.R-project.org/package=PropClust). The check with gcc 8.1 (https://www.stats.ox.ac.uk/pub/bdr/gcc8/PropClust.out) produced a warning about an uninitialized variable. I cannot reproduce the warning

On Mon, Sep 8, 2014 at 7:00 PM, Samuel F Antao <sfantao at us.ibm.com> wrote: > Alexey, Alexander, > > Thanks for the suggestions. I tried removing the flag SA_NODEFER but it > didn't do any good... I have been digging into the problem with the > null_deref test today but I was unable to clearly identify the problem. I > suspect that it was either a bug with the

Note that I've set the SA_NODEFER flag for the SEGV handler in the ASan runtime only a couple of days ago. Not sure that could've affected this test though; without that flag the second SEGV would've simply crashed the program. But you can try removing the flag from compiler-rt/trunk/lib/sanitizer_common/sanitizer_posix_libcdep.cc and see if that makes any difference. HTH, Alex On

Dear R.oo package users, while testing some functionality of the R.oo, I found that during the first construction of a object from a class, the constructor is twice called, but only one object is finalized. In all subsequent creation processes, the constructor is (expectedly) called once. Here some example code: library(R.oo) setConstructorS3("Test_class",function(val) {

There are two misspellings in the german Error message for friedman test: Fehler in friedman.test.default(cont$score, group = cont$goup, blocks = cont$cont) : y, Gruppen und blöcke müssen die sekbe Länge haben The correct spelling would be: Fehler in friedman.test.default(cont$score, group = cont$goup, blocks = cont$cont) : y, Gruppen und *Blöcke* müssen die *selbe* Länge haben Instead of

CRAN (and crantastic) updates this week New packages ------------ * EffectStars (1.0) Maintainer: Unknown Author(s): Gunther Schauberger License: GPL-2 http://crantastic.org/packages/EffectStars The package provides functions to visualize regression models with categorical response. The effects of the covariates are plotted with star plots in order to allow for an optical

Dear R People: I'm building a packages on an Ubuntu Karmic Koala 9.10 system and am getting the following errors: * checking PDF version of manual ... WARNING LaTeX errors when creating PDF version. This typically indicates Rd problems. LaTeX errors found: ! Font T1/ptm/m/n/10=ptmr8t at 10.0pt not loadable: Metric (TFM) file not found . <to be read again> relax l.7

In the example below, the Memory Sanitizier (from clang 3.3) reports an error: #include <math.h> int main() { double x; (void) modf(0, &x); if (x) { // Boom return 1; } return 0; } I see that modf() is not implemented by compiler-rt. Is it possible to make the Memory Sanitizer assume that all un-instrumented functions initialize any pointers arguments?

Hello everyone, I have noticed that there is a BoundsChecking.c under lib/Transforms/Instrumentation/. I am wondering how to use this tool and which type of bugs it targets. Are the tool provide the same functionality with Address Aanitizer? Thanks a lot -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Fri, Apr 11, 2014 at 12:35 AM, Kostya Serebryany <kcc at google.com> wrote: > > I wonder if we can configure the lit test runner to print the (tail of) > test output on failure. > You'd have to teach FileCheck, actually, since it's the one that consumes stderr in this case. Rather than doing that, why not use *SAN_OPTIONS=log_file=blah.txt, and teach lit to dump that

Hi there, I'm trying to use the memory sanitizer of LLVM 3.3. It's crashing during MSan initialization (__msan::InitShadow). Here's the strace output. mmap(0x400000000000, 35184372088831, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0x400000000000 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x55edf4b36720} --- +++ killed by SIGSEGV (core

I'm compiling compiler-rt via CMake+Ninja on x86_64+ArchLinux and one of the tests fails on ToT: MemorySanitizer :: chained_origin_with_signals.cc The text expects uninitialized warnings while the execution prints nothing, thus FileCheck fails. Anyone seeing this? cheers, --renato

Folks, Am I right to assume that if I specify { 'category' : "sanitizer" } to my buildboc config on builders.py, it'll only fire builds on "compiler-rt" repository changes? One of our buildbots, http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-full, is mainly a compiler-rt tester, and most of the time it fails for problems in the sanitizers (as intended),

On 29 July 2014 15:02, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote: > You mean replacing SIGUSR1 with SIGHUP in the test case? Weird, I > don't see how they are different. So, AFAIK, they should be identical. But I put some printfs and sleeps around and it wasn't a synchronization issue. My man page says that SIGUSR1 should terminate if there isn't a handler for

This bot was failing from http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/29505 until it went green on http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/29534 Anyone happen to know why? I can't quite figure it out from the commits - would be good to know if it's a buildbot issue or a genuine LLVM problem that was in the LLVM code and fixed by one of those

On 04/10/2018 05:22 AM, Han Han wrote: > Hi, > I tried to compile libvirt with address sanitizer( > https://github.com/google/sanitizers/wiki/AddressSanitizer) to discover > memory errors. But fails when make. > Code version: > $ git describe > v4.2.0-92-g3f204e4de > > Compile tools: > automake 1:1.15.1-3 all [installed] > clang-7 1:7~svn323616-1 amd64

Actually it only link the shlib fine. Linking any executable against it fails: llvm[2]: Linking Release+Asserts executable llvm-lto (without symbols) /home/kfischer/julia/deps/llvm-svn/build_Release+Asserts/Release+Asserts/bin/clang++ -fsanitize=address -O3 -Wl,-R -Wl,'$ORIGIN/../lib' -L/home/kfischer/julia/deps/llvm-svn/build_Release+Asserts+Sanitize/Release+Asserts/lib

Hello I am willing to make changes in Address Sanitizer for experimentation. But as I am a naive user I am confused with the fact that if I make changes to Address Sanitizer do I have to rebuild the whole LLVM. Could somebody please help me figure out a way in which I can make changes to address sanitizer and do not have to compile the whole LLVM. Aayushi Agrawal -------------- next part

Why does GN bot still send mails? I thought it got fixed? On Wed, Jul 3, 2019 at 1:44 PM <llvm.buildmaster at lab.llvm.org> wrote: > > The Buildbot has detected a new failure on builder sanitizer-x86_64-linux-gn while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-gn/builds/1820 > > Buildbot URL:

Why is there a public GN buildbot that sends emails and IRC notifications? That isn't what was agreed upon. Either un-GM it, or silence it. Roman. On Fri, Jun 28, 2019 at 1:05 AM <llvm.buildmaster at lab.llvm.org> wrote: > > The Buildbot has detected a new failure on builder sanitizer-x86_64-linux-gn while building llvm. > Full details are available at: >