Wayne.Zhang at barclayscapital.com
2011-Mar-08 14:24 UTC
[Rd] How to disable R's crash prompt
Dear R devel, I have a C++ app that calls into embedded R to perform some analytic calculations. When my app encounters a segmentation fault, R always prints the following crash prompt and asks me to enter an action: *** caught segfault *** address 0x8, cause 'memory not mapped' Possible actions: 1: abort (with core dump, if enabled) 2: normal R exit 3: exit R without saving workspace 4: exit R saving workspace The problem is my app will be run in non-interactive mode, so there is no way for me to enter the action. Is there a way to disable the crash prompt and have R simply crash the whole app? I have tried using "-file=/dev/null", "-slave", "-vanilla", and pretty much all other start options, to no avail. Thanks in advance for your help, Wayne _______________________________________________ This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group. _______________________________________________ [[alternative HTML version deleted]]
On Tue, 8 Mar 2011, Wayne.Zhang at barclayscapital.com wrote:> Dear R devel, > > I have a C++ app that calls into embedded R to perform some analytic > calculations. When my app encounters a segmentation fault, R always > prints the following crash prompt and asks me to enter an action: > > > *** caught segfault *** > address 0x8, cause 'memory not mapped' > > Possible actions: > 1: abort (with core dump, if enabled) > 2: normal R exit > 3: exit R without saving workspace > 4: exit R saving workspace > > > > The problem is my app will be run in non-interactive mode, so there > is no way for me to enter the action. Is there a way to disable theR does not do that in 'non-interactive mode'. Take a look at the code: that section is conditional on R_Interactive.> crash prompt and have R simply crash the whole app? I have tried > using "-file=/dev/null", "-slave", "-vanilla", and pretty much all > other start options, to no avail.They do not control if R is interactive: the front-end (yours, I presume since you mention embedding but do not otherwise give any details) does.> Thanks in advance for your help, > > Wayne-- Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595
On 8 March 2011 at 09:24, Wayne.Zhang at barclayscapital.com wrote:
| Dear R devel,
|
| I have a C++ app that calls into embedded R to perform some analytic
calculations. When my app encounters a segmentation fault, R always prints the
following crash prompt and asks me to enter an action:
|
|
| *** caught segfault ***
| address 0x8, cause 'memory not mapped'
|
| Possible actions:
| 1: abort (with core dump, if enabled)
| 2: normal R exit
| 3: exit R without saving workspace
| 4: exit R saving workspace
|
|
|
| The problem is my app will be run in non-interactive mode, so there is no way
for me to enter the action. Is there a way to disable the crash prompt and have
R simply crash the whole app? I have tried using "-file=/dev/null",
"-slave", "-vanilla", and pretty much all other start
options, to no avail.
Are you using RInside? You could try rebuilding it with the this (from
src/RInside.cpp) set to true
bool verbose = false;
as well as with possibly more debugging output added to the RInside
destructor (where I removed a few commented-out lines for brevity):
RInside::~RInside() { // now empty as MemBuf is internal
logTxt("RInside::dtor BEGIN", verbose);
R_dot_Last();
R_RunExitFinalizers();
R_CleanTempDir();
Rf_endEmbeddedR(0);
logTxt("RInside::dtor END", verbose);
instance_ = 0 ;
}
to at least confirm that you get here. And if you really,really wanted to I
suppose you could try to do without some of these cleanup and finalizer
functions. But I think that would send you into somewhat uncharted territory,
so you probably want to do read Section 8.1 ("8.1 Embedding R under
Unix-alikes") of Writing R Extension carefully. Best bet may still be to
avoid the segfault alltogether if you can.
Hope this helps, Dirk
--
Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com
On Tue, Mar 8, 2011 at 2:24 PM, <Wayne.Zhang at barclayscapital.com> wrote:> Dear R devel, > > I have a C++ app that calls into embedded R to perform some analytic calculations. ?When my app encounters a segmentation fault, R always prints the following crash prompt and asks me to enter an action: > > > *** caught segfault *** > address 0x8, cause 'memory not mapped' > > Possible actions: > 1: abort (with core dump, if enabled) > 2: normal R exit > 3: exit R without saving workspace > 4: exit R saving workspace > > > > The problem is my app will be run in non-interactive mode, so there is no way for me to enter the action. ?Is there a way to disable the crash prompt and have R simply crash the whole app? ?I have tried using "-file=/dev/null", "-slave", "-vanilla", and pretty much all other start options, to no avail.If someone from Barclays Capital is writing programs that are being allowed to seg fault and they want to *ignore* the seg fault then I'm taking all my money away from Barclays Capital and keeping it away. Barclays Capital, the bank that likes to say "seg fault". Your code can't possibly seg fault - our governments are always telling us banks are too big to fail. That's enough banker bashing. Barry