Core dump with R --encoding=foo -e 1 (non-existing encoding)
On 13-07-28 1:31 PM, Henrik Bengtsson wrote:
Trying to launch R with a *non-existing* encoding core dumps/crashes, e.g. R --encoding=foo -e 1. EXAMPLES:
R --encoding=foo -e 1
R version 3.0.1 (2013-05-16) -- "Good Sport" Copyright (C) 2013 The R Foundation for Statistical Computing Platform: x86_64-apple-darwin10.8.0 (64-bit) [...]
*** caught segfault *** address 0xffffffffffffffff, cause 'memory not mapped' aborting ... Segmentation fault % R --encoding=foo -e 1 R version 3.0.0 (2013-04-03) -- "Masked Marvel" Copyright (C) 2013 The R Foundation for Statistical Computing Platform: x86_64-unknown-linux-gnu (64-bit) [...]
<ERROR: re-encoding failure from encoding 'foo'>
(not sure if the above is a core dump, but the expression is not echoed/evaluated) %R --encoding=foo -e 1 (also Rterm --encoding=foo -e 1) R Under development (unstable) (2013-07-26 r63419) -- "Unsuffered Consequences" Copyright (C) 2013 The R Foundation for Statistical Computing Platform: x86_64-w64-mingw32/x64 (64-bit) [...] [crashes "R for Windows terminal front-end"] Should I file a bug report?
The general rule is that if a crash like that occurs in both the release version (which is 3.0.1, not 3.0.0) and R-patched, you should file a bug report. If it only occurs in R-patched or in R-devel, then a message to this list is probably better. If it only occurs in the release but not R-patched, then no report is necessary: it has been fixed. Duncan Murdoch