Great, that works for me, thanks!
If this is an issue with glibc, has it been reported to the glibc devs, and
are they working on a fix?
On Tue, Jun 9, 2020 at 9:12 PM Prof Brian Ripley
wrote:
> It is known, with a known workaround, see e.g.
>
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
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)
