cffi-devel June 2009

cffi-devel@common-lisp.net

11 participants
20 discussions

[cffi-devel] Foreign structures by value
by Liam Healy 26 Aug '10

26 Aug '10

I have written Foreign Structures By Value (FSBV) to allow calling foreign functions while passing or returning structures by value. It uses CFFI and libffi. It currently provides two macros for users, fsbv:defcstruct and fsbv:foreign-funcall, which are used exactly like their CFFI counterparts. It works for small test cases I've tried, but probably could use some improvement. If the keepers of CFFI are interested, I would be happy for it to be included in CFFI. In the meantime, it can be found here: http://repo.or.cz/w/fsbv.git Thank you. Liam

2 3

[cffi-devel] %load-foreign-library on SBCL
by Elliott Slaughter 27 Jan '10

27 Jan '10

Hi, I have a question about the implementation of %load-foreign-library on SBCL. It seems that the call to load-shared-object remembers the absolute pathname to the library that is loaded unless :dont-save t is used. This causes portability issues for my application, which can't load from the same path when used on different systems. Is there any reason to choose this behavior? Of course, with :dont-save t, the user then has to call use-foreign-library again when starting up from the saved image, but I find this preferable to the crash I receive otherwise. An example patch is included below. Thanks. --- src/cffi-sbcl.lisp~ 2009-04-14 19:33:40.000000000 -0700 +++ src/cffi-sbcl.lisp 2009-04-03 15:28:37.000000000 -0700 @@ -324,7 +324,7 @@ (defun %load-foreign-library (name path) "Load a foreign library." (declare (ignore name)) - (load-shared-object path)) + (load-shared-object path :dont-save t)) ;;; SBCL 1.0.21.15 renamed SB-ALIEN::SHARED-OBJECT-FILE but introduced ;;; SB-ALIEN:UNLOAD-SHARED-OBJECT which we can use instead. -- Elliott Slaughter "Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay

3 10

[cffi-devel] [PATCH] 64-bit support for Allegro, and allocate stack objects in the static area
by John Fremlin 17 Jul '09

17 Jul '09

Happy new year! On 64-bit Allegro, run (cffi:defcfun strerror :string (errnum :int)) (strerror 1) and you will probably get Received signal number 4 (Illegal instruction) [Condition of type EXCL:SYNCHRONOUS-OPERATING-SYSTEM-SIGNAL] at least if the returned pointer is more than 32-bits. The problem is that without this patch, cffi-allegro.lisp does not support 64-bit pointers. Does the patch address the problem properly? It seems to work for us. The use of :unsigned-nat instead of :unsigned-long is recommended by Franz because on Windows 64-bit :unsigned-long is still 32-bits. --- a/addons/cffi_0.10.3/src/cffi-allegro.lisp +++ b/addons/cffi_0.10.3/src/cffi-allegro.lisp @@ -135,7 +135,7 @@ SIZE-VAR is supplied, it will be bound to SIZE during BODY." ;; stack allocation pattern `(let ((,size-var ,size)) (declare (ignorable ,size-var)) - (ff:with-stack-fobject (,var '(:array :char ,size)) + (ff:with-stack-fobject (,var '(:array :char ,size) :allocation :foreign-static-gc) (let ((,var (ff:fslot-address ,var))) ;; (excl::stack-allocated-p var) => T ,@body)))) @@ -263,12 +263,12 @@ SIZE-VAR is supplied, it will be bound to SIZE during BODY." :unsigned-long) 'integer) (:float 'single-float) (:double 'double-float) - (:foreign-address :foreign-address) + (:foreign-address 'integer) (:void 'null)))) (defun foreign-allegro-type (type) (if (eq type :foreign-address) - nil + :unsigned-nat type)) (defun allegro-type-pair (type)

4 17

Re: [cffi-devel] allocating :count 0 in clisp
by Luís Oliveira 30 Jun '09

30 Jun '09

On Tue, Jun 30, 2009 at 3:13 PM, Tobias Rautenkranz<tobias(a)rautenkranz.ch> wrote: > I had something like in man malloc in mind: > "If size is 0, then malloc() returns either NULL, or a unique pointer value > that can later be successfully passed to free()." How about making CFFI:FOREIGN-ALLOC always return a null pointer regardless of what malloc() would do? Would that work? > I need this for: > QByteArray ( const char * data, int size ) > I guess the malloc definition should also be fine for stuff like: > ssize_t write(int fd, const void *buf, size_t count); > > Requiring a null pointer might be to restrictive; SBCL e.g.: > (cffi:foreign-string-alloc "" :null-terminated-p nil) > #.(SB-SYS:INT-SAP #X080961A8) > 0 -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/

2 1

[cffi-devel] allocating :count 0 in clisp
by Tobias Rautenkranz 30 Jun '09

30 Jun '09

(cffi:foreign-string-alloc "" :null-terminated-p nil) gives an error in CLISP: *** - FFI:FOREIGN-ALLOCATE: element type has size 0: #(FFI:C-ARRAY FFI:UINT8 0) The problem is that FFI:FOREIGN-ALLOCATE does not allow the allocation of arrays of size zero. Not sure where to fix this.

2 1

[cffi-devel] New patches: 25-Jun-2009
by Luis Oliveira 26 Jun '09

26 Jun '09

Thu Jun 25 12:43:15 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Don't trim #\VT. M ./grovel/grovel.lisp -1 +1 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-090625.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi-cffi;a=summary

1 0

[cffi-devel] New patches: 22-Jun-2009
by Luis Oliveira 23 Jun '09

23 Jun '09

Mon Jun 22 17:52:52 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Groveler: trim-whitespace not strip-whitespace. M ./grovel/grovel.lisp -1 +1 Mon Jun 22 17:33:53 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Groveler: fix typo. M ./grovel/grovel.lisp -1 +1 Mon Jun 22 17:26:26 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Groveler: small refactoring, create *EXE-EXTENSION* M ./grovel/grovel.lisp -4 +6 Mon Jun 22 17:18:57 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Groveler: move boilerplate C code to common.h M ./cffi-grovel.asd +1 A ./grovel/common.h M ./grovel/grovel.lisp -51 +6 Mon Jun 22 16:51:42 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Groveller: fix usage of *CC-FLAGS*. M ./doc/cffi-manual.texinfo -2 +2 M ./grovel/grovel.lisp -16 +23 Mon Jun 22 16:13:24 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Include <string.h> with the groveler boilerplate code. M ./grovel/grovel.lisp +1 Mon Jun 22 16:03:17 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Move the DEFPACKAGE and INVOKE out of grovel.lisp M ./cffi-grovel.asd -1 +3 M ./grovel/grovel.lisp -100 A ./grovel/invoke.lisp A ./grovel/package.lisp Mon Jun 22 15:45:57 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Style change. M ./grovel/grovel.lisp -1 +1 Mon Jun 22 15:04:29 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Groveler: use WITH-STANDARD-IO-SYNTAX when processing grovel files. M ./grovel/grovel.lisp -16 +18 Mon Jun 22 15:03:26 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Groveler: implement %INVOKE for ABCL. M ./grovel/grovel.lisp -1 +11 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-090622.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi-cffi;a=summary

1 0

[cffi-devel] New patches: 16-Jun-2009
by Luis Oliveira 17 Jun '09

17 Jun '09

Tue Jun 16 12:20:07 EDT 2009 Luis Oliveira <loliveira(a)common-lisp.net> tagged 0.10.5 Tue Jun 16 12:19:44 EDT 2009 Luis Oliveira <loliveira(a)common-lisp.net> * update cffi.asd for version 0.10.5 M ./cffi.asd -1 +1 Tue Jun 16 12:18:26 EDT 2009 Luis Oliveira <loliveira(a)common-lisp.net> * cffi-manual: minor style change. M ./doc/cffi-manual.texinfo -5 +7 Tue Jun 16 12:05:19 EDT 2009 Stelian Ionescu <sionescu(a)common-lisp.net> * Update docs for groveler clause CONSTANT. M ./doc/cffi-manual.texinfo -1 +3 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-090616.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi-cffi;a=summary

1 0

[cffi-devel] Thread callback problem
by Bodhi 17 Jun '09

17 Jun '09

Hi, I'm trying to write a wrapper to Apple's CoreMIDI framework with CFFI. CoreMIDI midi input is callback based, the framework creates a thread for you and then calls your given callback on that thread. I wrapped the necessary functions but whenever my program receives midi it crashes to the ldb debugger with a bus error (signal 10). After digging around for a while I came across the following thread: http://common-lisp.net/pipermail/cffi-devel/2009-May/003121.html According to the thread I can't callback into lisp on a non-lisp-created thread. Is there anyway to 'bless' a thread so i can callback to lips? Or is the only way to buffer the input in the C thread and then access it from a separate lisp thread? (I'm a lisp beginner using SBCL by the way.) Maybe it would be nice to put a note in the callback part of the CFFI manual warning about this gotcha? Thanks for any help or pointers, Bodhi

3 2

[cffi-devel] New patches: 15-Jun-2009
by Luis Oliveira 16 Jun '09

16 Jun '09

Mon Jun 15 13:07:33 EDT 2009 Luis Oliveira <loliveira(a)common-lisp.net> * grovel: remove comment about the *CC* and the CC environment variable We already do look at CC in GROVEL::CC-COMPILE-AND-LINK. M ./grovel/grovel.lisp -1 Mon Jun 15 11:13:12 EDT 2009 Luis Oliveira <loliveira(a)common-lisp.net> * cffi-grovel: use "cc" on non-Windows platforms (including Cygwin) M ./grovel/grovel.lisp -5 +3 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-090615.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi-cffi;a=summary

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel June 2009