From: David Pirotte <david@altosw.be>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Matija Obid <matija.obid@posteo.net>, guile-user@gnu.org
Subject: Re: G-Golf - Callback segmentation fault
Date: Thu, 5 Sep 2024 18:23:06 -0300 [thread overview]
Message-ID: <20240905182306.77491907@tintin> (raw)
In-Reply-To: <87frqe4kd2.fsf@pelzflorian.de>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
> P.S. on Guix, I also no longer have to use --no-grafts, possibly
> because Guix had major updates to core packages.
Excellent!
> G-golf really satisfies now.
At last! Note that the above was not a g-golf problem [1].
Regards,
David
[1]
And for that matter, nor is (a g-golf problem) the patch i just added
to adapt to a GI/libffi api change that i was unaware of [2] - up to
this upstream api change, g-golf has never failed to build and run an
ffi-closure, ever since it implements callback and vfunc, all (the
closure marshal machinery) entirely written in scheme by the way.
[2]
the gi doc tells us switch to call g-callable-info-create-closure when
using gi >= 1.71.0, but fails to tells us that, starting with gi >=
1.72.0, the ffi-closure pointer we receive is no longer a 'native
executable code pointer' ...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-09-05 21:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 14:50 G-Golf - Callback segmentation fault Matija Obid
2024-08-21 15:19 ` pelzflorian (Florian Pelz)
2024-08-23 23:57 ` David Pirotte
2024-08-24 16:01 ` pelzflorian (Florian Pelz)
2024-08-25 5:09 ` David Pirotte
2024-08-25 13:28 ` pelzflorian (Florian Pelz)
2024-08-26 6:40 ` pelzflorian (Florian Pelz)
2024-08-22 0:21 ` David Pirotte
2024-08-27 20:09 ` Matija Obid
2024-08-28 10:50 ` pelzflorian (Florian Pelz)
2024-08-29 0:18 ` David Pirotte
2024-08-31 16:35 ` Matija Obid
2024-09-02 15:30 ` pelzflorian (Florian Pelz)
2024-09-02 21:18 ` David Pirotte
2024-09-03 1:01 ` David Pirotte
2024-09-05 4:00 ` David Pirotte
2024-09-05 7:24 ` pelzflorian (Florian Pelz)
2024-09-05 7:42 ` pelzflorian (Florian Pelz)
2024-09-05 21:23 ` David Pirotte [this message]
2024-09-05 21:44 ` David Pirotte
2024-09-05 20:48 ` David Pirotte
2024-09-05 13:37 ` Matija Obid
2024-09-05 22:14 ` David Pirotte
2024-09-06 6:29 ` David Pirotte
2024-09-06 9:44 ` pelzflorian (Florian Pelz)
2024-09-06 18:37 ` David Pirotte
2024-09-06 22:08 ` David Pirotte
2024-09-06 23:16 ` David Pirotte
2024-09-07 14:08 ` pelzflorian (Florian Pelz)
2024-09-07 11:53 ` Matija Obid
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=20240905182306.77491907@tintin \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=matija.obid@posteo.net \
--cc=pelzflorian@pelzflorian.de \
/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).