==8061== Invalid read of size 1
==8061== at 0x4EC0F63: ??? (in /usr/lib/R/lib/libR.so)
...
> ==8061== Address 0x4231f7a3c8360000 is not stack'd, malloc'd or (recently)
free'd
Is that the first complaint from valgrind while running the program?
It's better to work on the first complaint. In general, anything after
the first complaint from valgrind(memcheck) is less trustworthy.
The error that memcheck detected might taint anything that is derived from it.
Anyway, the libR.so code at 0x4EC0F63 tried to fetch one byte from address
0x4231f7a3c8360000
which was not a valid address. Valgrind complained, then let the program
fetch from that address, so the program got SIGSEGV because there was nothing
in the address space at that address. The Rstudio code caught the SIGSEGV
and aborted execution.
One way to get more information is to invoke valgrind with:
valgrind --vgdb-error=0 other_valgrind_args /path/to/Rstudio
Rstudio_args
and follow the directions. Open another terminal window, run gdb on
/path/to/Rstudio,
then copy+paste the "target remote ..." command into the gdb session. Then
enter:
(gdb) continue
When valgrind complains, then the gdb session will gain control. Look around:
(gdb) info proc ## get the PID
(gdb) shell cat /proc/PID/maps ## look at the address space mappings
and so on. If this does not give good clues then it may be necessary
to insert debugging printf() into your C code in order to see what is happening.
Please tell us the valgrind version ("valgrind --version") and the hardware
architecture.
--
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
