Thanks Jacob,
I'll see if I can figure out why interrupt handling isn't working
properly. I'm guessing that something is awry in restoring Python's
interrupt handler code after returning from R's evaluator.
-G
On Mar 27, 2007, at 1:39PM , Jacob Joseph wrote:
> Pressing ctrl-c while r is pr
Pressing ctrl-c while r is processing always works properly. Pressing
ctrl-c after "from rpy import *" does not guarantee a segfault
immediately, but a crash is virtually certain within 2-10 repetitions of
ctrl-c.
For clarity, once R displays the "possible actions", keyboard input goes
to pyt
On Mar 26, 2007, at 3:46PM , Jacob Joseph wrote:
> Gregory, thanks for the quick assistance.
>
> If I manage to press ctrl-c while still in rpy.py:__call__(), I can
> get
> back to the python shell,
It looks like r's signal handler is doing its thing corrrectly,
> and get a segfault at exit
Hmm. Try this code instead, maybe it'll be slow enough to ensure you
can get it while still inside of call():
>> from rpy import r
>> r("for(i in 1:1e6) rnorm(1e6)")
On Mar 26, 2007, at 3:46PM , Jacob Joseph wrote:
> Gregory, thanks for the quick assistance.
>
> If I manage to pres
Gregory, thanks for the quick assistance.
If I manage to press ctrl-c while still in rpy.py:__call__(), I can get
back to the python shell, and get a segfault at exit from this shell.
At other times, it will segfault immediately. Pressing ctrl-c a second
time in rapid succession seems with my
Hi Jacob,
It looks like the event handler code isn't properly setting or
resetting the control-c handler. Can you try seeing whether Control
C is handled correctly while R itself is processing. IE, exectute:
from rpy import r
r("for(i in 1:1e6) 1+1")
then press Control-C.
Linux.
Sorry, I didn't even think to include it.
-Jacob
On 03/26/2007 02:47 PM, Gregory. R. Warnes wrote:
> What O/S?
>
>
>
> On Mar 26, 2007, at 11:36AM , Jacob Joseph wrote:
>
>> Hi folks,
>> I'm looking for suggestions to correct a crash caused by R. Often,
>> upon
>> pressing ctrl-C a
What O/S?
On Mar 26, 2007, at 11:36AM , Jacob Joseph wrote:
> Hi folks,
> I'm looking for suggestions to correct a crash caused by R. Often,
> upon
> pressing ctrl-C after importing rpy, R segfaults. I need not have yet
> accessed rpy for this to occur. Here's a sample:
>
> *** caught se
Hi folks,
I'm looking for suggestions to correct a crash caused by R. Often, upon
pressing ctrl-C after importing rpy, R segfaults. I need not have yet
accessed rpy for this to occur. Here's a sample:
*** caught segfault ***
address (nil), cause 'unknown'
Possible actions:
1: abort (with c
Hi folks,
I'm looking for suggestions to correct a crash caused by R. Often, upon
pressing ctrl-C after importing rpy, R segfaults. I need not have yet
accessed rpy for this to occur. Here's a sample:
*** caught segfault ***
address (nil), cause 'unknown'
Possible actions:
1: abort (with cor
10 matches
Mail list logo
