Message-ID: <BANLkTi=6sqs25XCNuJ-UZhEZHb+nBZ5Jzw@mail.gmail.com>
Date: 2011-04-19T17:58:57Z
From: Douglas Bates
Subject: [Rcpp-devel] Segfault in R-devel CMD check Rcpp
In-Reply-To: <BANLkTin1BeLg=o9Kajn=e1v4-VmTN5q6Pg@mail.gmail.com>
Sorry - I misspoke. The segfault was with R-2.13.0, the Ubuntu
maverick amd_64 build.
On Tue, Apr 19, 2011 at 12:55 PM, Douglas Bates <bates at stat.wisc.edu> wrote:
> Rcpp from SVN version 3004 is segfaulting on me in the unit tests at
> test.sugar.asvector
>
> Executing test function test.sugar.asvector ?...
> ?*** caught segfault ***
> address 0x3, cause 'memory not mapped'
>
> Traceback:
> ?1: .Primitive(".Call")(<pointer: 0x7f69e75854c7>, x, y, z)
> ?2: fx(1:4, 1:5, diag(1:5))
> ?3: func()
> ?4: system.time(func())
> ?5: doTryCatch(return(expr), name, parentenv, handler)
> ?6: tryCatchOne(expr, names, parentenv, handlers[[1L]])
> ?7: tryCatchList(expr, classes, parentenv, handlers)
>
> I'll check other versions of R first. ?Next I'll see what happens with
> gctorture and --enable-write-barrier
>
> Is anyone else encountering this?
>