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

Re: Problem loading in SBCL on Mojave
by Patrick May 24 Mar '19

24 Mar '19

Thanks, I wasn’t aware of that. Here’s the results of using asdf: > sbcl This is SBCL 1.5.0, 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. * (asdf:load-system :cffi) ; compiling file "/Users/Patrick/.sbcl/site/cffi_0.9.2/src/cffi-sbcl.lisp" (written 08 SEP 2006 04:56:43 PM): ; compiling (DEFPACKAGE #:CFFI-SYS ...) ; compiling (IN-PACKAGE #:CFFI-SYS) ; compiling (MAPC (LAMBDA # ...) ...) ; compiling (DEFUN CANONICALIZE-SYMBOL-NAME-CASE ...) ; compiling (DEFUN POINTERP ...) ; compiling (DEFUN POINTER-EQ ...) ; compiling (DEFUN NULL-POINTER ...) ; compiling (DEFUN NULL-POINTER-P ...) ; compiling (DEFUN INC-POINTER ...) ; compiling (DEFUN MAKE-POINTER ...) ; compiling (DEFUN POINTER-ADDRESS ...) ; compiling (DEFUN %FOREIGN-ALLOC ...) ; compiling (DEFUN FOREIGN-FREE ...) ; compiling (DEFMACRO WITH-FOREIGN-POINTER ...) ; compiling (DEFUN MAKE-SHAREABLE-BYTE-VECTOR ...) ; compiling (DEFMACRO WITH-POINTER-TO-VECTOR-DATA ...) ; compiling (DEFMACRO DEFINE-MEM-ACCESSORS ...) ; compiling (DEFINE-MEM-ACCESSORS (:CHAR SB-SYS:SIGNED-SAP-REF-8) ...) ; compiling (DEFUN CONVERT-FOREIGN-TYPE ...) ; compiling (DEFUN %FOREIGN-TYPE-SIZE ...) ; compiling (DEFUN %FOREIGN-TYPE-ALIGNMENT ...) ; compiling (DEFUN FOREIGN-FUNCALL-TYPE-AND-ARGS ...) ; compiling (DEFMACRO %%FOREIGN-FUNCALL ...) ; compiling (DEFMACRO %FOREIGN-FUNCALL ...) ; compiling (DEFMACRO %FOREIGN-FUNCALL-POINTER ...) ; compiling (DEFVAR *CALLBACKS* ...) ; compiling (DEFMACRO %DEFCALLBACK ...) ; compiling (DEFUN %CALLBACK ...) ; compiling (DEFUN %LOAD-FOREIGN-LIBRARY ...); ; caught ERROR: ; READ error during COMPILE-FILE: ; ; Lock on package SB-ALIEN violated when interning SHARED-OBJECT-FILE while in ; package CFFI-SYS. ; See also: ; The SBCL Manual, Node "Package Locks" ; ; (in form starting at line: 306, column: 0, position: 10629) ; compilation aborted after 0:00:00.139 debugger invoked on a UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<THREAD "main thread" RUNNING {10005205B3}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "cffi" "src" "cffi-sbcl"> Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry compiling #<CL-SOURCE-FILE "cffi" "src" "cffi-sbcl">. 1: [ACCEPT ] Continue, treating compiling #<CL-SOURCE-FILE "cffi" "src" "cffi-sbcl"> as having been successful. 2: Retry ASDF operation. 3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 4: Retry ASDF operation. 5: Retry ASDF operation after resetting the configuration. 6: [ABORT ] Exit debugger, returning to top level. (UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T "~/asdf-action::format-action/" ((#<ASDF/LISP-ACTION:COMPILE-OP > . #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "cffi-sbcl">))) ; File has been modified since compilation: ; SYS:CONTRIB;ASDF;UIOP.LISP.NEWEST ; Using form offset instead of character position. source: (ERROR 'COMPILE-FILE-ERROR :CONTEXT-FORMAT CONTEXT-FORMAT :CONTEXT-ARGUMENTS CONTEXT-ARGUMENTS) 0] 6 ; ; compilation unit aborted ; caught 2 fatal ERROR conditions ; caught 1 ERROR condition * (quit) > On Mar 23, 2019, at 5:15 PM, Robert Goldman <rpgoldman(a)sift.info> wrote: > > One thing to try first off -- quickload by default suppresses errors (catches them) and keeps you from getting at them. So you should do the (asdf:load-system :cffi) again, but this time get a backtrace. That will give people more information so that they can help. > Cheers, > R > > On 23 Mar 2019, at 15:56, Patrick May wrote: > > I’m running Mojave 10.14.2 and SBCL 1.5.0. When I try to load CFFI, I get this error: > > * (ql:quickload :cffi) > To load "cffi": > Load 1 ASDF system: > cffi > ; Loading "cffi" > [package cffi-utils].............................. > [package cffi-features]........................... > [package cffi-sys]....; > ; caught ERROR: > ; READ error during COMPILE-FILE: > ; > ; Lock on package SB-ALIEN violated when interning SHARED-OBJECT-FILE while in > ; package CFFI-SYS. > ; See also: > ; The SBCL Manual, Node "Package Locks" > ; > ; (in form starting at line: 306, column: 0, position: 10629) > > Then I’m dumped into the debugger. The same thing occurs using (asdf:load-system :cffi). I’ve cleared ~/.cache/common-lisp, but no joy. Any thoughts appreciated. > > Thanks, > > Patrick > > Robert P. Goldman > Research Fellow > Smart Information Flow Technologies (d/b/a SIFT, LLC) > > 319 N. First Ave., Suite 400 > Minneapolis, MN 55401 > > Voice: (612) 326-3934 > Email: rpgoldman(a)SIFT.net <mailto:rpgoldman@SIFT.net>

2 2

Problem loading in SBCL on Mojave
by Patrick May 23 Mar '19

23 Mar '19

I’m running Mojave 10.14.2 and SBCL 1.5.0. When I try to load CFFI, I get this error: * (ql:quickload :cffi) To load "cffi": Load 1 ASDF system: cffi ; Loading "cffi" [package cffi-utils].............................. [package cffi-features]........................... [package cffi-sys]....; ; caught ERROR: ; READ error during COMPILE-FILE: ; ; Lock on package SB-ALIEN violated when interning SHARED-OBJECT-FILE while in ; package CFFI-SYS. ; See also: ; The SBCL Manual, Node "Package Locks" ; ; (in form starting at line: 306, column: 0, position: 10629) Then I’m dumped into the debugger. The same thing occurs using (asdf:load-system :cffi). I’ve cleared ~/.cache/common-lisp, but no joy. Any thoughts appreciated. Thanks, Patrick

1 0

Question re. Call-by-value for foreign structs
by paul tarvydas 07 Dec '18

07 Dec '18

Using CFFI, do I need to specify translation methods when performing call-by-value to C? I am assuming (possibly incorrectly?) that cffi:defcstruct will create the translations for a C struct for me, then pass that struct by value to a Go foreign routine. Specifically, I am trying to call routines in Go from Lisp using a Lisp string. A Go string is a C struct { pointer-to-string , integer-length-of-string } Simple test code is in https://github.com/guitarvydas/lisp-go/blob/master/string-example/lisp-clie…. (see function "my-log", run "make" which should build and run the example, causing a NO-APPLICABLE-METHOD-ERROR). thanks pt

2 1

Nix / Guix compatibility
by Pierre Neidhardt 19 May '18

19 May '18

CFFI fails to find libraries on Nix / Guix. This is (probably) because those two distributions don't follow the traditional filesystem hierarchy /lib, /usr/lib, etc. For instance, trying to load sqlite-lib yields the following backtrace: --8<---------------cut here---------------start------------->8--- Unable to load any of the alternatives: ("libsqlite3.so.0" "libsqlite3.so") [Condition of type LOAD-FOREIGN-LIBRARY-ERROR] Restarts: 0: [RETRY] Try loading the foreign library again. 1: [USE-VALUE] Use another library instead. 2: [TRY-RECOMPILING] Recompile sqlite-ffi and try loading it again 3: [RETRY] Retry loading FASL for #<CL-SOURCE-FILE "sqlite" "sqlite-ffi">. 4: [ACCEPT] Continue, treating loading FASL for #<CL-SOURCE-FILE "sqlite" "sqlite-ffi"> as having been successful. 5: [RETRY] Retry ASDF operation. --more-- Backtrace: 0: (CFFI::FL-ERROR "Unable to load any of the alternatives:~% ~S" ("libsqlite3.so.0" "libsqlite3.so")) 1: (CFFI::TRY-FOREIGN-LIBRARY-ALTERNATIVES SQLITE3-LIB ("libsqlite3.so.0" "libsqlite3.so") NIL) 2: ((FLET CFFI::%DO-LOAD :IN CFFI::%DO-LOAD-FOREIGN-LIBRARY) #<FOREIGN-LIBRARY SQLITE3-LIB> SQLITE3-LIB (:OR "libsqlite3.so.0" "libsqlite3.so")) 3: (LOAD-FOREIGN-LIBRARY SQLITE3-LIB :SEARCH-PATH NIL) 4: (SB-FASL::LOAD-FASL-GROUP #S(SB-FASL::FASL-INPUT :STREAM #<SB-SYS:FD-STREAM for "file /home/ambrevar/.cache/common-lisp/sbcl-1.4.4-linux-x64/home/ambrevar/quicklisp/dists/quicklisp/software/cl-sqlite-.. 5: (SB-FASL::LOAD-AS-FASL #<SB-SYS:FD-STREAM for "file /home/ambrevar/.cache/common-lisp/sbcl-1.4.4-linux-x64/home/ambrevar/quicklisp/dists/quicklisp/software/cl-sqlite-20130615-git/sqlite-ffi.fasl" {100.. 6: ((FLET SB-FASL::THUNK :IN LOAD)) 7: (SB-FASL::CALL-WITH-LOAD-BINDINGS #<CLOSURE (FLET SB-FASL::THUNK :IN LOAD) {7FFFF6E4E31B}> #<SB-SYS:FD-STREAM for "file /home/ambrevar/.cache/common-lisp/sbcl-1.4.4-linux-x64/home/ambrevar/quicklisp/d.. 8: ((FLET SB-FASL::LOAD-STREAM :IN LOAD) #<SB-SYS:FD-STREAM for "file /home/ambrevar/.cache/common-lisp/sbcl-1.4.4-linux-x64/home/ambrevar/quicklisp/dists/quicklisp/software/cl-sqlite-20130615-git/sqlite.. 9: (LOAD #P"/home/ambrevar/.cache/common-lisp/sbcl-1.4.4-linux-x64/home/ambrevar/quicklisp/dists/quicklisp/software/cl-sqlite-20130615-git/sqlite-ffi.fasl" :VERBOSE NIL :PRINT NIL :IF-DOES-NOT-EXIST T :E.. 10: (UIOP/UTILITY:CALL-WITH-MUFFLED-CONDITIONS #<CLOSURE (LAMBDA NIL :IN UIOP/LISP-BUILD:LOAD*) {1002424CEB}> ("Overwriting already existing readtable ~S." #(#:FINALIZERS-OFF-WARNING :ASDF-FINALIZERS))) 11: ((SB-PCL::EMF ASDF/ACTION:PERFORM) #<unused argument> #<unused argument> #<ASDF/LISP-ACTION:LOAD-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "sqlite" "sqlite-ffi">) 12: ((LAMBDA NIL :IN ASDF/ACTION:CALL-WHILE-VISITING-ACTION)) 13: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS (ASDF/LISP-ACTION:LOAD-OP ASDF/LISP-ACTION:CL-SOURCE-FILE)) #<ASDF/LISP-ACTION:LOAD-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "sqlite" "sqlite-ffi">) [fast-met.. 14: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS :AROUND (T T)) #<ASDF/LISP-ACTION:LOAD-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "sqlite" "sqlite-ffi">) [fast-method] 15: ((:METHOD ASDF/PLAN:PERFORM-PLAN (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {10021FC613}>) [fast-method] 16: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT)) 17: ((:METHOD ASDF/PLAN:PERFORM-PLAN :AROUND (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {10021FC613}>) [fast-method] 18: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION ASDF/COMPONENT:COMPONENT)) #<ASDF/LISP-ACTION:LOAD-OP > #<ASDF/SYSTEM:SYSTEM "sqlite"> :PLAN-CLASS NIL :PLAN-OPTIONS NIL) [fast-method] 19: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> #<ASDF/LISP-ACTION:LOAD-OP > #<ASDF/SYSTEM:SYSTEM "sqlite"> :VERBOSE NIL) 20: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 21: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) #<ASDF/LISP-ACTION:LOAD-OP > #<ASDF/SYSTEM:SYSTEM "sqlite"> :VERBOSE NIL) [fast-method] 22: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> ASDF/LISP-ACTION:LOAD-OP "sqlite" :VERBOSE NIL) 23: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 24: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/LISP-ACTION:LOAD-OP "sqlite" :VERBOSE NIL) [fast-method] 25: (ASDF/SESSION:CALL-WITH-ASDF-SESSION #<CLOSURE (LAMBDA NIL :IN ASDF/OPERATE:OPERATE) {10021F140B}> :OVERRIDE T :KEY NIL :OVERRIDE-CACHE T :OVERRIDE-FORCING NIL) 26: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 27: (ASDF/SESSION:CALL-WITH-ASDF-SESSION #<CLOSURE (LAMBDA NIL :IN ASDF/OPERATE:OPERATE) {10021E896B}> :OVERRIDE NIL :KEY NIL :OVERRIDE-CACHE NIL :OVERRIDE-FORCING NIL) 28: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/LISP-ACTION:LOAD-OP "sqlite" :VERBOSE NIL) [fast-method] 29: (ASDF/OPERATE:LOAD-SYSTEM "sqlite" :VERBOSE NIL) 30: (QUICKLISP-CLIENT::CALL-WITH-MACROEXPAND-PROGRESS #<CLOSURE (LAMBDA NIL :IN QUICKLISP-CLIENT::APPLY-LOAD-STRATEGY) {10021E88CB}>) 31: (QUICKLISP-CLIENT::AUTOLOAD-SYSTEM-AND-DEPENDENCIES "sqlite" :PROMPT NIL) 32: ((:METHOD QL-IMPL-UTIL::%CALL-WITH-QUIET-COMPILATION (T T)) #<unused argument> #<CLOSURE (FLET QUICKLISP-CLIENT::QL :IN QUICKLISP-CLIENT:QUICKLOAD) {10021D574B}>) [fast-method] 33: ((:METHOD QL-IMPL-UTIL::%CALL-WITH-QUIET-COMPILATION :AROUND (QL-IMPL:SBCL T)) #<QL-IMPL:SBCL {10054D58E3}> #<CLOSURE (FLET QUICKLISP-CLIENT::QL :IN QUICKLISP-CLIENT:QUICKLOAD) {10021D574B}>) [fast-me.. 34: ((:METHOD QUICKLISP-CLIENT:QUICKLOAD (T)) :SQLITE :PROMPT NIL :SILENT NIL :VERBOSE NIL) [fast-method] 35: (QL-DIST::CALL-WITH-CONSISTENT-DISTS #<CLOSURE (LAMBDA NIL :IN QUICKLISP-CLIENT:QUICKLOAD) {10021CD67B}>) 36: (SB-INT:SIMPLE-EVAL-IN-LEXENV (QUICKLISP-CLIENT:QUICKLOAD :SQLITE) #<NULL-LEXENV>) 37: (EVAL (QUICKLISP-CLIENT:QUICKLOAD :SQLITE)) 38: (SB-EXT:INTERACTIVE-EVAL (QUICKLISP-CLIENT:QUICKLOAD :SQLITE) :EVAL NIL) 39: (SB-IMPL::REPL-FUN NIL) 40: ((LAMBDA NIL :IN SB-IMPL::TOPLEVEL-REPL)) 41: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA NIL :IN SB-IMPL::TOPLEVEL-REPL) {100335BB1B}>) 42: (SB-IMPL::TOPLEVEL-REPL NIL) 43: (SB-IMPL::TOPLEVEL-INIT) 44: ((FLET SB-UNIX::BODY :IN SB-EXT:SAVE-LISP-AND-DIE)) 45: ((FLET "WITHOUT-INTERRUPTS-BODY-27" :IN SB-EXT:SAVE-LISP-AND-DIE)) 46: ((LABELS SB-IMPL::RESTART-LISP :IN SB-EXT:SAVE-LISP-AND-DIE)) --8<---------------cut here---------------end--------------->8--- Any idea on how to fix this? -- Pierre Neidhardt

2 5

Memory fault error
by Elliott Johnson 01 May '18

01 May '18

Hello, If this is not the correct list to report a user error, I apologize and will happily redirect my question where ever suitable. I've been using cffi to make a trivial library to libsensors https://github.com/groeck/lm-sensors and am getting an odd memory fault error when referencing a string value from a groveled struct. After hitting my head against a wall for a day and a half, I thought I'd ask in case it's a simple mistake. Here's my information: Running a 64 bit linux install. My local version of the libsensors library is as follows: > elliott@desktop ~ $ file /usr/lib64/libsensors.so.4.4.0 > /usr/lib64/libsensors.so.4.4.0: ELF 64-bit LSB shared object, x86-64, > version 1 (SYSV), dynamically linked, stripped > elliott@desktop ~ $ sensors --version > sensors version 3.4.0+git_83cafd29f28d463573750d897014ec7143217ae5 > with libsensors version 3.4.0+git_83cafd29f28d463573750d897014ec7143217ae5 I'm using a fairly recent version of sbcl built from source that (apparently) passed all of the tests after the build: > CL-USER> (lisp-implementation-version) > "1.4.6.140-f8d5864d0" My version of cffi appears to be the latest: > CL-USER> (slot-value (asdf:find-system :cffi) 'asdf:version) > "0.19.0" My system uses cffi-grovel and defines the following structs: > (cstruct sensors-bus-id "sensors_bus_id" > (type "type" :type :short) > (nr "nr" :type :short)) > > (cstruct sensors-chip-name "sensors_chip_name" > (prefix "prefix" :type :string) > (bus "bus" :type (:struct sensors-bus-id)) > (address "addr" :type :int) > (path "path" :type :string)) These are based upon the definitions in sensors/sensors.h: https://github.com/groeck/lm-sensors/blob/master/lib/sensors.h After asdf loading the system, the following groveler definitions are created (had to dig these out of the cached build files): > (cffi:defcstruct (sensors-bus-id :size 4) > (type :short :offset 0) > (nr :short :offset 2)) > (cl:defconstant size-of-sensors-bus-id (cffi:foreign-type-size > '(:struct sensors-bus-id))) > (cffi:defcstruct (sensors-chip-name :size 24) > (prefix :string :offset 0) > (bus (:struct sensors-bus-id) :offset 8) > (address :int :offset 12) > (path :string :offset 16)) > (cl:defconstant size-of-sensors-chip-name (cffi:foreign-type-size > '(:struct sensors-chip-name))) All of the above appears to be correct, so I proceed to load the library: > (define-foreign-library libsensors > (:unix (:or "libsensors.so.4" "libsensors.so")) > (t (:default "libsensors.so"))) > (use-foreign-library libsensors) No issues, so I define a c function from the c header file that parses a sensor chip name-string into a struct: > (defcfun ("sensors_parse_chip_name" cffi-sensors-parse-chip-name) :int > "Parse a chip name to the internal representation. Return 0 on > success, <0 on error." > (orig-name :string) > (res (:pointer (:struct sensors-chip-name)))) Which is based upon the following header function declaration: > int sensors_parse_chip_name(const char *orig_name, sensors_chip_name > *res); Then I implement a simple call to print out the parsed values (not including the bus): > (defun test-sensors-parse-chip-name (string) > (with-foreign-object (name '(:struct sensors-chip-name)) > (unless (= 0 (cffi-sensors-parse-chip-name string name)) > (error "Failed to parse: ~A" string)) > (with-foreign-slots ((prefix address path) > name > (:struct sensors-chip-name)) > (format t "~%Prefix: '~A'" prefix) > (format t "~%Address: '~A'" address) > (format t "~%Path: '~A'" path)))) The above when executed gives the following output before the error: > CL-LMSENSORS> (test-sensors-parse-chip-name "atk0110-acpi-0") > > Prefix: 'atk0110' > Address: '0' And once it tries to access the path variable, it gives the following error (sorry a lot rolls off the screen): > Unhandled memory fault at #xE71B7. > [Condition of type SB-SYS:MEMORY-FAULT-ERROR] > > Restarts: > 0: [RETRY] Retry SLIME REPL evaluation request. > 1: [*ABORT] Return to SLIME's top level. > 2: [ABORT] abort thread (#<THREAD "repl-thread" RUNNING {1002207F93}>) > > Backtrace: > 0: (CFFI::FOREIGN-STRING-LENGTH #.(SB-SYS:INT-SAP #X000E71B7) > :ENCODING :UTF-8 :OFFSET 0) > Locals: > #:.DEFAULTING-TEMP. = :UTF-8 > #:.DEFAULTING-TEMP.#1 = 0 > #:N-SUPPLIED-0 = 1 > POINTER = #.(SB-SYS:INT-SAP #X000E71B7) > 1: (FOREIGN-STRING-TO-LISP #.(SB-SYS:INT-SAP #X000E71B7) :OFFSET 0 > :COUNT NIL :MAX-CHARS 4611686018427387900 :ENCODING :UTF-8$ > Locals: > #:.DEFAULTING-TEMP. = 0 > #:.DEFAULTING-TEMP.#1 = NIL > #:.DEFAULTING-TEMP.#2 = 4611686018427387900 > #:.DEFAULTING-TEMP.#3 = :UTF-8 > ENCODING = :UTF-8 > #:N-SUPPLIED-0 = 1 > POINTER = #.(SB-SYS:INT-SAP #X000E71B7) > 2: ((:METHOD TRANSLATE-FROM-FOREIGN (T CFFI::FOREIGN-STRING-TYPE)) > #.(SB-SYS:INT-SAP #X000E71B7) #<CFFI::FOREIGN-STRING-TYPE $ > 3: (TEST-SENSORS-PARSE-CHIP-NAME "atk0110-acpi-0") My guess is I'm not defining the (:struct sensors-chip-name) correctly, so that when sensors_parse_chip_name writes values into the struct, it somehow overlaps into the path string. When looking at the source for sensors_parse_chip_name I've noticed that it does not set or access the path value at all. So I decided to write a small c program to test the native behavior: > elliott@desktop ~ $ cat test-sensors.c > #include <stdio.h> > #include <stdlib.h> > #include "sensors/sensors.h" > > int main( ) { > > //sensors_init( NULL ); > > struct sensors_chip_name name; > > int return_value = sensors_parse_chip_name( "atk0110-acpi-0", &name); > if ( return_value != 0 ) { > printf( "Failed to get a good return value." ); > exit( return_value ); > } > > printf( "Printing the prefix: '%s'\n", name.prefix ); > printf( "Address: '%i'\n", name.addr ); > printf( "Printing path value: '%s'\n", name.path ); > printf ("\n exiting..." ); > > exit( 0 ); > } > elliott@desktop ~ $ gcc test-sensors.c -l sensors -o test-sensors > elliott@desktop ~ $ ./test-sensors > Printing the prefix: 'atk0110' > Address: '0' > Printing path value: '' > > exiting... No problems there, so I assume that the issue is all my lack of cffi-fu training. Any pointers (yes, pun intended) would be appreciated... sorry for such a long read, but I hope it helps to have the background. At the very least it helped me to frame the issue in my mind by writing this. Regards, Elliott

2 4

RFC: INLINE defcfun and auto FTYPE declarations [with patch]
by Andrzej Walczak 13 Nov '17

13 Nov '17

Dear CFFI developers! Recently we have migrated one of our largest projects from our home-grown foreign-function interface implementation to CFFI. The project is almost 1M LOC with almost 1K of foreign-functions. Previously, we have inlined all of our foreign-function stubs. We also use FTYPEs through the code for type-safety and optimization. Having CFFI functions inlined and FTYPEs generated would spare us from writing those declarations on our own. The attached patch contains a proposal that we would like to share. Please, let us know about any modification necessary that would make this patch useful for a larger community. FYI: We have tested the patch against about a hundredth open-source Lisp projects. Kindly, -- Andrzej Walczak (Google/ITA Software Engineer)

3 6

allow user to specify his own path and version of libssl
by Anton Vodonosov 24 Sep '17

24 Sep '17

2 1

is it possible to effect stack allocation of foreign pointers
by james anderson 07 Sep '17

07 Sep '17

good afternoon; it appears that, where a field from a foreign structure is a pointer, when its value is extracted, the foreign pointer value requires allocation on the heap. is there some declaration combination which causes the foreign pointer to be allocated on the stack. for example, in the case below, the only space used is that to marshal the arguments to %compare-quad. as insignificant as it may seem, for sustained use, the effect is to require frequent collection of the equivalent of the full heap, which brings with it promotion issues. it would be beneficial to cause the lhs-quad and rhs-quad values to be on the stack. is there some means to do that? as is evident, this particular case involves sbcl, but - as far as cffi is concerned, the question is general. — (cffi:defcstruct #.(swig-lispify "MDB_val" 'classname) (#.(swig-lispify "mv_size" 'slotname) :pointer) (#.(swig-lispify "mv_data" 'slotname) :pointer)) (declaim (type (function (SB-SYS:SYSTEM-AREA-POINTER SB-SYS:SYSTEM-AREA-POINTER) fixnum) %compare-quad)) (cffi:defcallback %compare-keys :int ((lhs :pointer) (rhs :pointer)) (%compare-lmdb-keys lhs rhs)) (defun %compare-lmdb-keys (lhs rhs) (declare (type SB-SYS:SYSTEM-AREA-POINTER lhs rhs) (optimize (speed 3) (safety 0) (space 3))) (let ((lhs-quad (cffi:foreign-slot-value lhs '(:struct liblmdb:val) 'liblmdb:mv-data)) (rhs-quad (cffi:foreign-slot-value rhs '(:struct liblmdb:val) 'liblmdb:mv-data))) (declare (dynamic-extent lhs-quad rhs-quad)) (%compare-quad lhs-quad rhs-quad))) (defun %compare-quad (lhs rhs) (declare (dynamic-extent lhs rhs) (optimize (speed 3) (safety 0))) (if (eql lhs rhs) 0 (loop for i below 4 for lhs_i = (cffi:mem-aref lhs 'term-id i) for rhs_i = (cffi:mem-aref rhs 'term-id i) if (< lhs_i rhs_i) return -1 if (> lhs_i rhs_i) return 1 finally (return 0)))) --- james anderson | james(a)dydra.com | http://dydra.com

2 2

foreign-type-size implementation
by james anderson 25 Aug '17

25 Aug '17

while profiling code which depends on foreign sizes, i observed that foreign-type-size was doing most of the work. this (so it seems) due to the circularity check. is there some reason that there is no logic to decide to push the process into compile-time where it is possible? something like: (define-compiler-macro foreign-type-size (&whole form type) (cond ((or (keywordp type) (typep type '(cons (eql :struct)))) (foreign-type-size type)) ((and (symbolp type) (constantp type)) (foreign-type-size (symbol-value type))) (t form)))

3 5

Hello.
by mike thomas 11 Aug '17

11 Aug '17

Hi there. Thanks for all the great work you do here. I had a problem loading cl-libuv from Quicklisp on Windows because the default installation location for the development package sits in C:/Program Files/libuv, which broke the grovel compilation. The include path list is split by the code below, fixed by removing the space from the separator list per the patch. It wasn't clear to me what parse-command-flags was meant to do, given the definitions in grovel.lisp of cl-libuv which control the header search paths. Is there a place to lodge bug reports on github for cffi? Maybe one needs to be a contributor? Cheers Mike @@ -33,7 +33,7 @@ ;;; Utils (defun parse-command-flags (flags) - (let ((separators '(#\Space #\Tab #\Newline #\Return))) + (let ((separators '(#\Tab #\Newline #\Return))) (remove-if 'emptyp (split-string flags :separator separators)))) (defun parse-command-flags-list (strings)

2 1