From osklyar at maninvestments.com  Mon Mar 30 11:09:28 2009
From: osklyar at maninvestments.com (Sklyar, Oleg (London))
Date: Mon, 30 Mar 2009 10:09:28 +0100
Subject: [Rd] CTRL-C during .Call causes R to quit to command line
In-Reply-To: <1e7471d50903292023y415529bcmdc0467139df17da@mail.gmail.com>
References: <1e7471d50903292023y415529bcmdc0467139df17da@mail.gmail.com>
Message-ID: <1A68FCB28DE72F4BA3B967E6506CCE43047DF7B2@mildnpexmb01.maninvestments.ad.man.com>

If you use JNI or rJava, you should start the VM with -Xrs argument,
otherwise the descibed things happen as Java catches the Ctrl-C
interrupt

Dr Oleg Sklyar
Research Technologist
AHL / Man Investments Ltd
+44 (0)20 7144 3107
osklyar at maninvestments.com 

> -----Original Message-----
> From: r-devel-bounces at r-project.org 
> [mailto:r-devel-bounces at r-project.org] On Behalf Of Saptarshi Guha
> Sent: 30 March 2009 04:24
> To: r-devel at r-project.org
> Subject: [Rd] CTRL-C during .Call causes R to quit to command line
> 
> Hello,
> During a .Call e.g
> while(TRUE){
>     value <-rhsqnextKVR(rdr)  ## has .Call in this function
>     if(is.null(value)) break;
>   }
> if I press CTRL-C, R exits straight to the command line.
> 
> Q: How can I prevent this? I should point out that my library uses
> JNI, so I'm not sure if that is causing it.
> I'm using R-2.8 on Linux (RHEL 5)
> Thank you in advance
> Regards
> Saptarshi
> 
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
> 

**********************************************************************
Please consider the environment before printing this email or its attachments.
The contents of this email are for the named addressees ...{{dropped:19}}



[Rd] CTRL-C during .Call causes R to quit to command line
Sklyar, Oleg (London