similar to: [LLVMdev] valgrind for BitCode

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: 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

Hi, only one letter got to valgrind-developers mailing list. I'll quote the first message of the thread so that those who do not read llvmdev knew what's this discusssion about. === Begin of the first message === > 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

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

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

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

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

I worked out why valgrind wasn't being applied to nbdkit when run by many of the tests (patches 1-2). Unfortunately I'm not able to make it actually fail tests when valgrind fails. Although the situation is marginally improved in that you can now manually examine the *.log files and find valgrind failures that way. Also adds valgrinding of the Python plugin (patch 3). Along the way I

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

When we are valgrinding we don't really care about the child processes, which might be qemu, libvirtd, etc. So disable tracing into children (at least, as far as is possible with valgrind, which is not entirely disabling it, but suppressing it). --- m4/guestfs_progs.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/guestfs_progs.m4 b/m4/guestfs_progs.m4 index

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

Previously posted here: https://www.redhat.com/archives/libguestfs/2015-June/msg00266.html Rich.

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.

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 >

Hi All Though, I have used clang which is great. I am dumb in LLVM design. Will somebody be kind enough to answer Will LLVM be suitable for developing valgrind like tools? Regards --Dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130107/84a92ae4/attachment.html>

Hi all, I'm on Ubuntu 18.04, running R-4.0.0 which I compiled from source, and using valgrind I am always seeing the following message. Does anybody else see that? Is that a known false positive? Any ideas how to fix/suppress? Seems related to TRE, do I need to upgrade that? (base) tdhock at maude-MacBookPro:~/R/binsegRcpp$ R --vanilla -d valgrind -e 'extSoftVersion()' ==9565==

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 +-

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

On Fri, Jan 13, 2012 at 10:31 PM, Villmow, Micah <Micah.Villmow at amd.com> wrote: > Also, this can be easily reproduced with the following command: > > valgrind --tool=memcheck --show-reachable=yes --leak-check=full > --track-origins=yes --leak-check=full opt -disable-opt -O0 <some random > bitcode file> > > > > Micah > Hi Micah, the

R CMD check --use-valgrind <packagename> used to run valgrind on the tests in the tests directory of the package. But it seems to have stopped. R-2.9.1 doesn't -- at least on my box -- and neither does R-2.10.0 (devel). I am not sure when this stopped. I think 2.8.x did this. The only old R I have around is 2.6.0 and it certainly does. R CMD check --help for 2.9.1 says (among other