From: Taylan Kammer <taylan.kammer@gmail.com>
To: Jan Synacek <jsynacek@redhat.com>, guile-user@gnu.org
Subject: Re: FFI questions
Date: Fri, 15 May 2020 22:09:22 +0200 [thread overview]
Message-ID: <6762c9b7-ad3d-3bf8-0b65-5d30bcb8ea38@gmail.com> (raw)
In-Reply-To: <CAPsXM8WZ7ORLOgoJMNqxfy7ZZKbptv+T2kpTsh=mc7e1V-K09w@mail.gmail.com>
On 15.05.2020 15:47, Jan Synacek wrote:
> Hello,
>
> Currently I have something like this:
>
> (define libxcb (dynamic-link "libxcb"))
>
> ...
>
> (define c-change-window-attributes
> (pointer->procedure void
> (dynamic-func "xcb_change_window_attributes" libxcb)
> (list '* uint32 uint32 '*)))
>
> (define (change-window-attributes conn win mask vals)
> (c-change-window-attributes conn win mask (bytevector->pointer vals)))
>
> The last argument to xcb_change_window_attributes is 'const void *' and I
> need to pass a u32 vector to it. As it is right now, it segfaults when I
> try passing #u32(something) to 'change-window-attributes'. Is it possible
> to make it accept a u32 vector using just Scheme or do I have to work
> around it on the C level?
I think the reason it segfaults might be that the #u32() object gets
garbage collected soon after you call bytevector->pointer on it. See
that you put it in a variable, and reference that variable at some point
after xcb_change_windor_attributes should be done with the vector, to
make sure that this is not the problem.
Otherwise I'm not sure why it should segfault. A #u32() bytevector
really should be backed by a contiguous array of uint32_t values, just
like what you'll get when you define a uint32_t[] in C.
> My second question is about FFI and structs. Is it possible to access C
> struct members from Scheme by name? If not, how do I generally approach the
> problem? I've checked how guile-xcb does it and it seems to be building
> hash tables with field names as keys. But that basically requires me to
> "redefine" all the C structs that I would be interested in at the Scheme
> level.
These might be useful:
https://github.com/TaylanUB/scheme-bytestructures
https://www.nongnu.org/nyacc/ffi-help.html
I maintain bytestructures, am happy to answer questions. (If I don't
respond on the mailing list, feel free to mail me directly or open an
issue on GitHub; mails with guile-user@gnu.org and guile-devel@gnu.org
in the To: or Cc: fields land in a folder that I don't always check.)
The FFI Helper is by Matt Wette who also hangs around on this mailing
list I believe.
- Taylan
next prev parent reply other threads:[~2020-05-15 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 13:47 FFI questions Jan Synacek
2020-05-15 20:09 ` Taylan Kammer [this message]
2020-05-15 23:52 ` Matt Wette
2020-05-15 23:59 ` Matt Wette
2020-05-17 10:06 ` Jan Synacek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6762c9b7-ad3d-3bf8-0b65-5d30bcb8ea38@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=guile-user@gnu.org \
--cc=jsynacek@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).