00:25 <bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-s390x/builds/1099 [default]

01:24 <mssun> cfbolz, simpson: "mssun: what mssun wants is possible. the pypy interpreter can be compiled together with an rpython program, and then you can just call the rpython methods of eg the objspace to run python code. the main downside is that the compilation times are a bit terrrible". Sorry for the late reply. I was trying to use libffi to call libpypy from rpython code. The problem is that many symbols/functions are shared.

02:00 <bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/4041 [py3.5]

02:00 <bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5774 [py3.5]

02:00 <bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7057 [py3.5]

02:00 <bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/4204 [py3.5]

02:00 <bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-32/builds/6123 [py3.5]

02:00 <bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/4888 [py3.5]

02:00 <bbot2> Started: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armel/builds/2524 [py3.5]

02:00 <bbot2> Started: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armhf-raspbian/builds/2285 [py3.5]

02:35 <bbot2> Failure: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armhf-raspbian/builds/2285 [py3.5]

03:01 <bbot2> Success: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armel/builds/2524 [py3.5]

03:03 <bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/4888 [py3.5]

03:14 <bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5774 [py3.5]

03:15 <bbot2> Success: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7057 [py3.5]

04:38 <bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/4041 [py3.5]

06:02 <bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-32/builds/6123 [py3.5]

09:36 <bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/4204 [py3.5]

16:18 <rjarry> hi all

16:18 <rjarry> I am looking for some insight on cffi

16:19 <rjarry> I have a C library that exports a function: int write_mem(char **strp, ....);

16:20 <rjarry> which allocates a string and sets the allocated buffer address to the given pointer

16:20 <rjarry> the caller is responsible for freeing the pointer

16:20 <rjarry> how do I call this from python code ?

16:20 <rjarry> I tried a lot of things, but none work

16:23 <tos9> rjarry: what did you try

16:24 <rjarry> buf = ffi.new('char *')

16:24 <rjarry> buf_p = ffi.new('char **', buf)

16:24 <rjarry> lib.write_mem(buf_p, ...)

16:24 <rjarry> lib.write_mem(ffi.addressof(buf), ...)

16:25 <rjarry> oh, it looks like this works:

16:25 <rjarry> buf = ffi.new('char **')

16:25 <rjarry> lib.write_mem(buf, ...)

16:25 <rjarry> and then, access buf[0]

16:26 <rjarry> but will the allocated memory be free automatically ?

16:45 <simpson> rjarry: Yes.

16:45 <rjarry> awesome, thanks

17:15 <antocuni> rjarry: make sure to keep "buf" alive

17:15 <antocuni> else the memory is freed as soon as buf.__del__ is called (which happens immediately when refcount==0 on CPython, and eventually when the GC runs on PyPy)

23:00 <bbot2> Started: http://buildbot.pypy.org/builders/own-linux-s390x/builds/1100 [default]