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 python or nowhere, but never the menu itself.
Thanks again.
-Jacob
On 03/26/2007 04:14 PM, Gregory Warnes wrote:
> 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 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 small samples to produce the
>> issue more frequently.
>>
>> I realize this doesn't resolve your question with more than a
>> "sometimes". Is there a case that might test this more definitively?
>>
>> -Jacob
>>
>> On 03/26/2007 03:21 PM, Gregory Warnes wrote:
>>> 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.
>>>
>>> -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?
>>>>>
>>>>>
>>>>>
>>>>> 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 segfault ***
>>>>>> address (nil), cause 'unknown'
>>>>>>
>>>>>> Possible actions:
>>>>>> 1: abort (with core dump)
>>>>>> 2: normal R exit
>>>>>> 3: exit R without saving workspace
>>>>>> 4: exit R saving workspace
>>>>>> Selection:
>>>>>> *** caught segfault ***
>>>>>> address 0x48, cause 'memory not mapped'
>>>>>>
>>>>>> Possible actions:
>>>>>> 1: abort (with core dump)
>>>>>> 2: normal R exit
>>>>>> 3: exit R without saving workspace
>>>>>> 4: exit R saving workspace
>>>>>> Selection:
>>>>>>
>>>>>> I'm running:
>>>>>> *rpy-1.0-RC2 patched with
>>>>>> https://sourceforge.net/tracker/?
>>>>>> func=detail&atid=453021&aid=1665794&group_id=48422
>>>>>>
>>>>>> *python 2.5
>>>>>> *ipython
>>>>>> *R 2.4.1
>>>>>> (all on x86_64)
>>>>>>
>>>>>> Thanks.
>>>>>> -Jacob
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list
