Setting options(device) to something dumb then plotting causes a segfault:
*** caught segfault ***
address 0x1b0, cause 'memory not mapped'
1: abort (with core dump, if enabled)
2: normal R exit
Yes, doing a dumb thing is dumb but if someone is developing new graphics devices then it might be nice if it was robust to things like this. I suspect the graphics system doesn't know that options(device) hasn't created a graphics device structure and blunders on regardless, smashing memory in the process.
Also happens on Windows and Mac.
R version 3.1.1 (2014-07-10)
Platform: x86_64-unknown-linux-gnu (64-bit)
 LC_CTYPE=en_GB.utf8 LC_NUMERIC=C
 LC_TIME=en_GB.utf8 LC_COLLATE=en_GB.utf8
 LC_MONETARY=en_GB.utf8 LC_MESSAGES=en_GB.utf8
 LC_PAPER=en_GB.utf8 LC_NAME=C
 LC_ADDRESS=C LC_TELEPHONE=C
 LC_MEASUREMENT=en_GB.utf8 LC_IDENTIFICATION=C
attached base packages:
 stats graphics grDevices utils datasets methods base