September 2012 - cffi-devel - mailman3.common-lisp.net

[cffi-devel] CFFI from git bug with :int64 struct fields?
by Alistair Gee 07 Nov '12

07 Nov '12

When using latest CFFI via clbuild2 (git:// common-lisp.net/projects/cffi/cffi.git) I encountered a problem with :int64 fields. CFFI seems to treat this field as (signed-byte 32). This is with SBCL x86-64 on Ubuntu 10.10: This is SBCL 1.0.55.1-6548750, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * (require :cffi) NIL * (cffi:defcstruct foo (a :int64)) FOO * (cffi:with-foreign-object (foo 'foo) (setf (cffi:foreign-slot-value foo 'foo 'a) 123456789012345)) ; in: CFFI:WITH-FOREIGN-OBJECT (FOO 'FOO) ; (SETF (CFFI:FOREIGN-SLOT-VALUE FOO 'FOO 'A) 123456789012345) ; --> LET* MULTIPLE-VALUE-BIND LET PROGN CFFI::FOREIGN-SLOT-SET SETF LET* ; --> MULTIPLE-VALUE-BIND LET PROGN CFFI::MEM-SET CFFI-SYS:%MEM-SET LET SETF ; ==> ; (SB-KERNEL:%SET-SIGNED-SAP-REF-32 FOO 0 #:VALUE14) ; ; caught WARNING: ; Derived type of #:VALUE14 is ; (VALUES (INTEGER 123456789012345 123456789012345) &OPTIONAL), ; conflicting with its asserted type ; (SIGNED-BYTE 32). ; See also: ; The SBCL Manual, Node "Handling of Types" ; ; compilation unit finished ; caught 1 WARNING condition debugger invoked on a SIMPLE-TYPE-ERROR in thread #<THREAD "initial thread" RUNNING {10029B97C3}>: Value of #:VALUE14 in (SB-KERNEL:%SET-SIGNED-SAP-REF-32 FOO 0 #:VALUE14) is 123456789012345, not a (SIGNED-BYTE 32). Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (SB-C::%COMPILE-TIME-TYPE-ERROR (123456789012345) (SIGNED-BYTE 32) #<unavailable argument> ((SB-KERNEL:%SET-SIGNED-SAP-REF-32 FOO 0 #:VALUE14) . #:VALUE14)) 0] 0

3 4

[cffi-devel] SBCL-1.0.58 / CFFI crash
by Ryan Pavlik 05 Nov '12

05 Nov '12

The following crashes for me with CFFI (master) and sbcl-1.0.58 (actually as early as sbcl-1.0.57-49-gd720bc3) on amd64/x86_64: https://gist.github.com/fa8f380a218b55b4ae6a (This is a simplified case of a callback being used in cl-cairo2.) Altering some things causes it not to crash: * Not declaring P with DYNAMIC-EXTENT. * Not using STATUS_T as a return type, simply using :INT and 0. * Altering the FORMAT to a simpler version. However, I don't think any of these things are in error, and my guess is there is some corruption that happens regardless. This works without error on earlier versions of SBCL as well as CCL, but it's unclear whether something bad is happening silently. Am I doing something wrong here, or is there a bug in CFFI or SBCL? thanks, -- Ryan Pavlik <rpavlik(a)gmail.com> | https://github.com/rpav 425.220.9585

2 3

[cffi-devel] Calling Lisp Function from C: How to declare this function in C land ?
by Frank Goenninger 22 Sep '12

22 Sep '12

(also posted to comp.lang.lisp) Hi all: I have a lisp image that contains the following functions: (defun frgo (a) (format *debug-io* "~%~A~&" a) (values)) (cffi:defcallback frgo_helper :void ((a-cstr :string)) (frgo (cffi:foreign-string-to-lisp a-cstr))) In a C dynamic library I have: * file frgo_c.h: extern void frgo_helper( char * a ); * file frgo_c.c: void frgo( char * a ) { frgo_helper( a ); } Now, the library does not compile - undefined symbol _frgo_helper() ! How do I make functions "known" to C land that are purely defined as callbacks in Lisp land? I tried to declare the function in C land like this: extern void frgo_helper( char * a ) __attribute__((weak_import)); No luck, though. My environment is: Mac OS X Snow Leopard (10.6.8), Apple LLVM compiler 3.0. An ideas / hints / tipps? Thanks a lot! Cheers Frank

2 2

[cffi-devel] C compilation error on sizeof structure
by Mirko Vukovic 21 Sep '12

21 Sep '12

Hello, cffi-grovel is failing to compile a file. I am not certain whether the problem is the way I am using cffi-grovel (most likely), my utter lack of knowledge of C, or something else. Also I noticed recent activity by Liam Healy on linking to structures (which I did not closely follow), and I wonder if it has any bearing on this. I want to link CL to "triangle", a library for two dimensional triangulation and meshing (http://www.cs.cmu.edu/~quake/triangle.html) The interface to the main subroutine is defined in "triangle.h" which defines a structure "triangulateio": struct triangulateio { REAL *pointlist; /* In / out */ REAL *pointattributelist; /* In / out */ int *pointmarkerlist; /* In / out */ int numberofpoints; /* In / out */ int numberofpointattributes; .... } I defined a groveller lisp file libtriangle-unix.lisp with the following contents: (define REAL "double") (include "/home/mv/external-libraries/c-code/triangle/triangle.h") (cstruct triangulateio "triangulateio") (Note that I did not specify any fields. I saw a post on the web suggesting that cffi would fill it in. Is that correct?) In the asd file, I have :components ((:file "cl-triangle-package-def") (cffi-grovel:grovel-file "libtriangle-unix"))) When I load the system, a C file is generated in ~/.cache/..., and this file fails to compile, on the statement containing "sizeof(triangulateio)" Here are the C file contents: #define REAL double #include "/home/mv/external-libraries/c-code/triangle/triangle.h" #include <grovel/common.h> int main(int argc, char**argv) { FILE *output = argc > 1 ? fopen(argv[1], "w") : stdout; fprintf(output, ";;;; This file has been automatically generated by " "cffi-grovel.\n;;;; Do not edit it by hand.\n\n"); fprintf(output, "(cl:in-package #:CL-TRIANGLE)\n\n"); /* cstruct section for TRIANGULATEIO */ fprintf(output, "(cffi:defcstruct ("); fprintf(output, "triangulateio"); fprintf(output, " :size %i)", sizeof(triangulateio)); /* Line 20 */ fprintf(output, ")\n"); ... The error message is libtriangle-unix.c: In function ‘main’: libtriangle-unix.c:20: error: ‘triangulateio’ undeclared (first use in this function) The same error happens if I modify the C file to explicitly declare the structure there. Two questions: - Is my procedure incorrect (the grove lisp file, asdf specification) - I don't see why triangulateio is undefined on line 20. But that may be my lack of C knowledge. Thanks, Mirko

2 1