From hb at biostat.ucsf.edu  Sun Jul 28 19:31:43 2013
From: hb at biostat.ucsf.edu (Henrik Bengtsson)
Date: Sun, 28 Jul 2013 10:31:43 -0700
Subject: [Rd] Core dump with R --encoding=foo -e 1 (non-existing encoding)
Message-ID: <CAFDcVCQKUQMs0D_TMLdDcONeEt90ws54UhFD17R8Lvsaumyqgw@mail.gmail.com>

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?

/Henrik



[Rd] Core dump with R --encoding=foo -e 1 (non-existing encoding)
Henrik Bengtsson