similar to: debug package calling C++ code using valgrind

valgrind complains about the save command in R 2.3.1 as shown by the script included below. Of course, I don't know whether this "Conditional jump or move depends on uninitialised value(s)" is really a bug. Experience with similar issues in my own code says it may be, but it is also hard to tell. Having no familiarity with the code cited in deflate.c, I leave the issue to experts.

By default valgrind suppresses many leaks. I'm not even sure exactly how it decides which ones to suppress, but certainly global variables pointing to malloc’d data are suppressed, which is not useful behaviour. Tell valgrind to show all leaks. It won't give an error on them. However to do this we also need a much more comprehensive list of suppressions so that we don't constantly

I had to add several suppressions because Python leaks memory by design, and also increase the max depth of valgrind stack traces because Python stack traces are very deep. Note that to do proper valgrinding of Python itself we would need to specially recompile Python: https://svn.python.org/projects/python/trunk/Misc/README.valgrind --- tests/test-lang-plugins.c | 3 +-

I think I am using objects according to the man page. This seems to be a valid regular expression. But whether I know what I'm doing or no, it still shouldn't be doing what valgrind seems to be saying it's doing. (IMHO) ---------- start of script ---------- Script started on Mon 01 Aug 2005 02:09:00 PM PDT linux$ printenv VALGRIND_OPTS --tool=3Dmemcheck linux$ cat bar.R foo <- 1

Full_Name: Martin Schlather Version: 2.10.0 OS: linux Submission from: (NULL) (91.3.220.231) Bug summary: some functions behave differently for NAs when valgrind is used in R, e.g. sum and prod Bug demonstration: --- without valgrind ---- > sum(c(NA,1)[1]) [1] NA --- with valgrind ---- > sum(c(NA,1)[1]) [1] NaN R call with valgrind: R -d "valgrind --tool=memcheck

Dear all, I'm trying to debug my R package with valgrind, but I cannot get past the point where I load make the data, as valgrind crashes when trying to extract a single time series object of a multivariate mts object. I'm using R 2.15.0 with platform x86_64-redhat-linux-gnu (64-bit). The valgrind.R contains code data(Seatbelts) y<-Seatbelts[,"VanKilled"] And I run

NUT developers, just thought I'd share some notes and ideas on using valgrind against the NUT USB drivers on Linux. Stepping back a bit, I wanted to make sure that the tripplite_usb driver* wasn't using any uninitialized memory, or leaking memory over time. valgrind (specifically, the memcheck tool) runs the code in a special dynamic translator that checks every memory access to see if

I am trying to do a classic R -d valgrind --vanilla < mypkg-Ex.R as described in http://cs.swan.ac.uk/~csoliver/ok-sat-library/internet_html/doc/doc/R/2.9.1/doc/manual/R-exts.html#Using-valgrind The problem is valgrind crashes imediately. I am using Ubuntu 10.04 LST (actually Biolinux) on a 64bit Dell Precision laptop with 4 core-i5 Intel processors. I have R-2-15-0 installed from source

--- extratests/suppressions | 20 ++++++++++++++++---- 1 files changed, 16 insertions(+), 4 deletions(-) diff --git a/extratests/suppressions b/extratests/suppressions index 97d4b78..78ca4ab 100644 --- a/extratests/suppressions +++ b/extratests/suppressions @@ -3,19 +3,19 @@ Memcheck:Cond fun:* fun:numa_node_size64 - fun:numa_init + obj:/usr/lib64/libnuma.so.1 } {

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 Mon, Dec 03, 2018 at 12:55:58PM -0600, Eric Blake wrote: > A GNU make-ism - but you already mention requiring GNU make in > README. Should we make ./configure error out hard if $MAKE is not > GNU Make, rather than risking someone getting 80% though a build on > BSD make and then choking when it gets here? Yes that would be a good idea as a separate patch. I'm always annoyed

I have ran under valgrind memcheck the process using libLLVM-2.9.so (rev.126022) and got several errors: ==24227== Invalid read of size 1 ==24227== at 0x40274C9: memcpy (mc_replace_strmem.c:497) ==24227== by 0x40D5B84: char* std::string::_S_construct<char const*>(char const*, char const*, std::allocator<char> const&, std::forward_iterator_tag) (in

Dear R developers I am running an instrumented build of R 2.6.1 on ubuntu, compiled with option configure --with-valgrind-instrumentation=3. If run valgrind R then I get all sorts of warnings. I was wondering whether I should worry about them or not. First, when I open R as follows: $R -d "valgrind --tool=memcheck --leak-check=full --show-reachable=yes" --vanilla I get a whole

As an update to the nouveau development community, the downstream fork of Valgrind with a mmap tracing tool ("mmt") we maintain has been rebased against the latest upstream release of Valgrind, v3.16.1 Code branch: https://github.com/envytools/valgrind/tree/mmt-3.16.1 Features of upstream Valgrind 3.16.x: https://www.valgrind.org/docs/manual/dist.news.html In selected highlights, the

If you've ever tried to use this option, you'll know that it didn't work well. It broke random things (probably RHBZ#1020216, definitely RHBZ#1023630), and caused random failures generally, while often not actually failing when valgrind itself found problems. This does not remove the guestfs_internal_exit API. That will instead be modified in a future commit. ---

Dear R People, in the R FAQ (in the R Programming section) it says ********************************************************************** How can I change compilation flags? =================================== Suppose you have C code file for dynloading into R, but you want to use `R CMD SHLIB' with compilation flags other than the default ones (which were determined when R was built).

It is known, with a known workaround, see e.g. https://www.stats.ox.ac.uk/pub/bdr/memtests/README.txt . Set suppressions in ~/.valgrindrc, e.g. the CRAN check machine has --suppressions=/data/blackswan/ripley/wcsrtombs.supp It is an issue in your OS (glibc), not TRE nor R. On 10/06/2020 00:21, Toby Hocking wrote: > Hi all, > > I'm on Ubuntu 18.04, running R-4.0.0 which I

This is a followup to the R-help thread, "Error: STRING_ELT() can only be applied to a 'character vector', not a 'builtin'". Thanks to Prof. Brian Ripley for suggesting the use of gctorture and valgrind. I am getting segmentation faults that appear to come from a memory leak. I now have a reproducible example (below). It requires the "g.data" package

Hi Andy, On Thu, 2007-08-09 at 01:12 +1000, Andy Kitchen wrote: > Hi All, > > > I'm currently learning llvm, for later use with a research project. I > thought a good way to learn would be to use it in a small to medium > sized project. A valgrind like tool for BitCode would work quite > nicely. Interesting idea :) > > > IR will made some things easier

Hi All, I'm currently learning llvm, for later use with a research project. I thought a good way to learn would be to use it in a small to medium sized project. A valgrind like tool for BitCode would work quite nicely. IR will made some things easier and somethings harder. Good things: * valgrind is very tightly tied to the underlying architecture, bcgrind can be totally platform