Re: [Rpy] segfault and 'release unlocked lock'

Hi Andrew, On Fri, May 9, 2008 at 1:24 PM, Andrew Dalke <[EMAIL PROTECTED]> wrote: > On May 7, 2008, at 1:02 AM, Andrew Dalke wrote: >> I've been having a lot of problems with intermittent crashes while >> using RPy under a rather old Python 2.4.2 install, with no Numeric >> support whatsoever. T

[Rpy] SF.net SVN: rpy: [511] trunk/rpy/TODO

Revision: 511 http://rpy.svn.sourceforge.net/rpy/?rev=511&view=rev Author: warnes Date: 2008-05-09 14:17:54 -0700 (Fri, 09 May 2008) Log Message: --- Add to TODO. Modified Paths: -- trunk/rpy/TODO Modified: trunk/rpy/TODO ==

[Rpy] SF.net SVN: rpy: [510] trunk/rpy/src/rpymodule.c

Revision: 510 http://rpy.svn.sourceforge.net/rpy/?rev=510&view=rev Author: warnes Date: 2008-05-09 14:16:59 -0700 (Fri, 09 May 2008) Log Message: --- Patch to correct link problem with R-2.7.0 Modified Paths: -- trunk/rpy/src/rpymodule.c Modified: trunk/rp

Re: [Rpy] segfault and 'release unlocked lock'

On May 7, 2008, at 1:02 AM, Andrew Dalke wrote: > I've been having a lot of problems with intermittent crashes while > using RPy under a rather old Python 2.4.2 install, with no Numeric > support whatsoever. This is all under Linux. > *** caught segfault *** > address 0x34b100, cause 'memory n