Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

I'm in no way knowledgeable about python (or R) internals, but for me this smells like Rpy putting some parts of it's initialisation into memory areas which are also accessed by other parts of the python interpreter. And that probably shouldn't happen... On 19 May 2011, at 23:18, Thomas Kluyv

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On 19 May 2011 22:00, Laurent Gautier wrote: > > Does > >>> import ri > >>> ri.R_VERSION_BUILD > correspond to the R version you are running rpy2 against ? > Yes: 2.12.1, svn rev 53855 > Do you have older versions of rpy2 installed ? If yes, does removing them > solve the problem ? I did hav

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On 2011-05-19 22:27, Thomas Kluyver wrote: On 19 May 2011 21:08, Laurent Gautier > wrote: >>> ri.NA_Real NA_real_ >>> import sys >>> sys.version '2.7.1+ (r271:86832, Mar 24 2011, 00:37:39) \n[GCC 4.5.2]' OK, that's interesting: >>> ri.NA_Real 0.0

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On 19 May 2011 21:08, Laurent Gautier wrote: > >>> ri.NA_Real > NA_real_ > >>> import sys > >>> sys.version > '2.7.1+ (r271:86832, Mar 24 2011, 00:37:39) \n[GCC 4.5.2]' > OK, that's interesting: >>> ri.NA_Real 0.0 >>> sys.version '2.7.1+ (r271:86832, Apr 11 2011, 18:05:24) \n[GCC 4.5.2]' The v

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On 2011-05-19 22:00, Thomas Kluyver wrote: On 19 May 2011 20:38, Artur Wroblewski > wrote: What version of gcc, binutils and glibc are you using? gcc 4.5.2 binutils 2.21.0 glibc 2.13 I don't compile Python myself, though - I let Ubuntu's build servers take c

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On 19 May 2011 20:38, Artur Wroblewski wrote: > What version of gcc, binutils and glibc are you using? > gcc 4.5.2 binutils 2.21.0 glibc 2.13 I don't compile Python myself, though - I let Ubuntu's build servers take care of that. > BTW. Interesting is, that every time (be it os.popen or now)

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On Thu, May 19, 2011 at 8:32 PM, Thomas Kluyver wrote: > On 19 May 2011 19:36, Artur Wroblewski wrote: >> >> At the moment the segfault can be reproduced as follows (using UCS4 >> based build) > > OK, interesting. I still can't replicate it, in either Python 2.7 or 3.2 > wide-unicode builds, with

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On 19 May 2011 19:36, Artur Wroblewski wrote: > At the moment the segfault can be reproduced as follows (using UCS4 > based build) > OK, interesting. I still can't replicate it, in either Python 2.7 or 3.2 wide-unicode builds, with 2.2.0 beta 3. Thomas --

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On Thu, May 19, 2011 at 12:46 PM, Artur Wroblewski wrote: [...] > While the os.popen does not cause my app to crash with UCS4, still > my application segfaults... just in different place. I will try to narrow it > and provide some stack trace later this evening. At the moment the segfault can be

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On Thu, May 19, 2011 at 11:16 AM, Christian Marquardt wrote: > Hmm, > I've been building our python (2.7.1) with --enable-unicode=ucs4 which I > believe stands for 4-byte Unicode. In any case, Rpy handles (should handle?) > the Unicode conversion through python C-API calls which should behave > co

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

Done - issue #74 Christian. On 14 May 2011, at 08:37, Laurent Gautier wrote: > Please use the bug tracker on bitbucket. > Otherwise there is a great chance this falls between the cracks. > > On 2011-05-13 17:49, Christian Marquardt wrote: >> Hello, >> >> I experienced seg faults and core

[Rpy] [ rpy-Bugs-3304515 ] Segmentation faults after importing RPy2 modules

Bugs item #3304515, was opened at 2011-05-19 12:28 Message generated for change (Tracker Item Submitted) made by cmarquardt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=453021&aid=3304515&group_id=48422 Please note that this message will contain a full copy of th

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

Hmm, I've been building our python (2.7.1) with --enable-unicode=ucs4 which I believe stands for 4-byte Unicode. In any case, Rpy handles (should handle?) the Unicode conversion through python C-API calls which should behave consistently with the way the original python has been build. As I s

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On 19 May 2011 08:19, Artur Wroblewski wrote: > On Thu, May 19, 2011 at 12:19 AM, Thomas Kluyver wrote: > > Ah, Unicode. I believe the builds from python.org are narrow unicode > (i.e. > > UTF-16), whereas those shipped in many Linux distros (including the one I > > use) are wide unicode (UTF-32

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

On Thu, May 19, 2011 at 12:19 AM, Thomas Kluyver wrote: > Ah, Unicode. I believe the builds from python.org are narrow unicode (i.e. > UTF-16), whereas those shipped in many Linux distros (including the one I > use) are wide unicode (UTF-32). This might explain why I can't replicate > your segfaul