Your "mocking" phrase in unknown to me. I am not sure where to trace that
down. Read the bash script for check? Read tools:::.check_packages?
Both are clear as mud to me.
Also I just tried debugging by print statements. That does not work. It
leaves the C called just before the crash. Putti
Agreed on divide-and-conquer. There is no other way. Valgridn et al may move
some code to registers for subtle changes.
On 4 July 2015 at 10:20, Charles Geyer wrote:
| I should add a more direct question. When a crash occurs ONLY when running R
| CMD check, how does one debug that? Usually one
I should add a more direct question. When a crash occurs ONLY when running
R CMD check, how does one debug that? Usually one would say that R CMD
check --use-valgrind
is the answer. But it only segfaults when --use-vagrind is not used. So
somehow we have to debug R CMD check itself. How?
On S
The diff for bar.Rout is OK. The solution is the same (the two matrices
have the same rows and so determine the same convex polyhedron). Why it
picks different orders of rows on different machines, I have no idea.
I also saw the pages of warnings from gcc -W -Wall -Wextra but they are all
about
Charles,
I took a look based on your tar ball. When I use the normal 'loud' setting I
default to for g++ (ie -pedantic -Wall) or clang++ I get more than a page
full of errors. I just tried it using the UBSAN-via-clang instrumented R I
provide via a docker container (and for which I showed usage
valgrind reports no errors
On Fri, Jul 3, 2015 at 4:44 PM, Gábor Csárdi wrote:
> On Fri, Jul 3, 2015 at 11:40 PM, Charles Geyer
> wrote:
> [...]
>
>> * run the file that causes the crash with R CMD check by itself,
>> it works, no crash
>> * run R CMD check --use-valgrind rcdd, it w
On Fri, Jul 3, 2015 at 11:40 PM, Charles Geyer wrote:
[...]
> * run the file that causes the crash with R CMD check by itself,
> it works, no crash
> * run R CMD check --use-valgrind rcdd, it works, no crash
> * run R CMD check --use-gct rcdd, it works no crash
> * use tools::chec
I am trying to update a CRAN package (rcdd) for the R-3.3.0 requirements.
And I think I have done it. But
When I do
R CMD check rcdd
one of the tests crashes (it says it caught a segfault). I am on an i686
box running Ubuntu 14.04 and the R is the one that comes from
http://cran.us.r-
