[Rd] valgrind crashing

[Prof Brian Ripley]

On 12/09/2012 06:56, David wrote:
>> 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 and configured using
>>
>> ./configure --enable-memory-profiling
>> --with-valgrind-instrumentation=2 --prefix=/usr/local/lib64/R-2.15.0-vg2
>>
>> in  /usr/local/bin there's a dynamic link
>>
>> R-2.15.0-vg2 -> /usr/local/lib64/R-2.15.0-vg2/bin/R
>>
>> I can run R in bash using
>>
>> $ R-2.15.0-vg2
>>
>> Valgrind was installed from the Ubuntu repositories using apt-get.
>
> Simply removing this version and installing from source got things working.

Yes, I was about to comment that your valgrind is far too old for an 
x86_64 system.  Even 3.7.x gave spurious reports.

>
> all the best
> David
>
>> But ...
>>
>> $ R-2.15.0-vg2 -d valgrind --vanilla
>> R-2.15.0-vg2 -d valgrind --vanilla
>> ==29007== Memcheck, a memory error detector
>> ==29007== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
>> ==29007== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h
>> for copyright info
>> ==29007== Command: /usr/local/lib64/R-2.15.0-vg2/lib64/R/bin/exec/R
>> --vanilla
>> ==29007==
>> --29007-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a
>>
>> valgrind: m_debuginfo/readdwarf.c:2292 (copy_convert_CfiExpr_tree):
>> Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
>> ==29007==    at 0x3802B1F7: ??? (in
>> /usr/lib/valgrind/memcheck-amd64-linux)
>>
>> sched status:
>>    running_tid=0
>>
>>
>> Note: see also the FAQ in the source distribution.
>> It contains workarounds to several common problems.
>> In particular, if Valgrind aborted or crashed after
>> identifying problems in your program, there's a good chance
>> that fixing those problems will prevent Valgrind aborting or
>> crashing, especially if it happened in m_mallocfree.c.
>>
>> If that doesn't help, please report this bug to: www.valgrind.org
>>
>> In the bug report, send all the above text, the valgrind
>> version, and what OS and version you are using.  Thanks.
>>
>>
>> I've used valgrind in the past on other computer without problem, but
>> I have no idea what's failling here (the FAQ didn't help). Does anyone
>> have any idea?
>>
>> many thanks
>> David
>>
>> p.s. I also have 2.15.1 installed in a near-identical manner as 2.15.0
>> with just the difference --with-valgrind-instrumentation=1, the result
>> is the same though.
>>
>
>


-- 
Brian D. Ripley,                  ripley at stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595