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
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
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
hen press Control-C.
>
> -G
>
> On Mar 26, 2007, at 2:48PM , Jacob Joseph wrote:
>
>> 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?
>&
port 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 press ctrl-c while still in rpy.py:__call__(), I can
>> get
>> b