cffi-devel March 2013

cffi-devel@common-lisp.net

7 participants
6 discussions

[cffi-devel] close-foreign-library assert
by nan 22 Mar '13

22 Mar '13

Hello again! I am working on a project which used to be completely in C++, now i am gradually moving some of it to CL. For this reason i need to work on both sides, which requires me to reload cffi bindings too often. I couldn't find anything related to this in documentation. Probably this is not an intended use case so there is no support. Which means i need to use my hammer again, restart image :) So, i started playing with load-foreign-library/close-foreign-library (probably not intended for this purpose) and whenever i call close-foreign-library with the result of load-foreign-library, i get this explosion: Inconsistency detected by ld.so: dl-close.c: 765: _dl_close: Assertion `map->l_init_called' failed! Tracing this assert shows it was triggered from dlclose system call in sbcl source, and i am not entirely sure where i should report this bug. I am still on archlinux using sbcl-git package from aur. Could it be another archlinux related bug? Thanks.

2 11

[cffi-devel] "Unhandled memory fault" on any memory allocation after fork
by agile software 21 Mar '13

21 Mar '13

Hi all ! First, thank you for your great work on this library. I just use it for the first time. I write the following code to test unix fork: =============================================== (asdf:oos 'asdf:load-op :cffi) (defpackage :testfork (:use :common-lisp :cffi)) (in-package :testfork) (defcvar "errno" :int) (cffi:defcfun ("getpid" unix-getpid) :int) (cffi:defcfun ("getuid" unix-getuid) :int) (cffi:defcfun ("getgid" unix-getgid) :int) (cffi:defcfun ("fork" unix-fork) :int) (cffi:defcfun ("exit" unix-exit) :void (code :int)) (cffi:defcfun ("wait" unix-wait) :int (statloc :pointer)) (when (zerop (unix-fork)) (with-foreign-pointer-as-string (str 6 str-size :encoding :ascii) (lisp-string-to-foreign "Hello, foreign world!" str str-size)) (unix-exit 0)) (progn (format t "I'm parent, Pid=~A~%" (unix-getpid)) (format t "one child claimed!~A~%" (unix-wait (cffi:null-pointer))) ) =============================================== When I add two lines using with-foreign-pointer-as-string and lisp-string-to-foreign, my SBCL always crashes, and tell me " fatal error encountered in SBCL pid XXXX: Unhandled memory fault. " I have tried other memory allocation macros, I get the same result. But if I remove them, the program runs and exits normally. What's the problem about allocating memory in child process? Or I use them in the wrong way? My environment is : OSX 10.8.3 Processor Intel Core i7, SBCL 1.0.55.0-abb03f9, cffi_0.10.7.1 installed from quicklisp Thank you very much!

2 2

[cffi-devel] always recompile with "asdf:load-system"
by iso 20 Mar '13

20 Mar '13

Hello everyone. Since this is my first post, thanks for the great library! After updating to new version (via quicklisp) i first had issues with my grovel file. I used to be able to reference types defined outside of grovel file, now i can't. I am not sure if it was a bug or a feature but somehow it compiled before! Anyways, after modifying a few things it is now working. My real problem is whenever i load a system based on cffi, project always compiles. With or without a change in the project. This is also started happening with the new version. I suspect it might be about grovel, loaded a few projects that is based on cffi, one uses cffi-grovel (static-vectors) the other one doesn't (cl-opengl). cl-opengl compiles at first time and then loads. cffi-grovel always compiles. Thanks.

5 10

[cffi-devel] always recompile with "asdf:load-system"
by nan 19 Mar '13

19 Mar '13

1 0

[cffi-devel] CFFI 0.11.0 released
by Luís Oliveira 09 Mar '13

09 Mar '13

CFFI 0.11.0 has been on Feb 25th, 2013, but I only finished writing the release notes today, which can be consulted at <https://github.com/cffi/cffi/wiki/NEWS>. My development focus for the next version will be on polishing the support for aggregate values (structs, arrays, etc), hopefully making sure the concept is well defined and consistently well support in various contexts (function calling, pointer referencing, struct slots, etc.). -- Luís Oliveira http://r42.eu/~luis/

1 0

[cffi-devel] Release blockers
by Stelian Ionescu 04 Mar '13

04 Mar '13

What is the minimum necessary that needs to be done(bugs to be fixed, etc...) to make a new release ? I want to dedicate this weekend to release CFFI because that blocks too many projects that depend on the new features, IOLib in primis. -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

4 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel March 2013