[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: G-Golf - Callback segmentation fault
From: |
David Pirotte |
Subject: |
Re: G-Golf - Callback segmentation fault |
Date: |
Thu, 5 Sep 2024 18:23:06 -0300 |
> 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' ...
pgpLL8skTDP_n.pgp
Description: OpenPGP digital signature
- Re: G-Golf - Callback segmentation fault, pelzflorian (Florian Pelz), 2024/09/02
- Re: G-Golf - Callback segmentation fault, Matija Obid, 2024/09/05
- Re: G-Golf - Callback segmentation fault, David Pirotte, 2024/09/05
- Re: G-Golf - Callback segmentation fault, David Pirotte, 2024/09/06
- Re: G-Golf - Callback segmentation fault, pelzflorian (Florian Pelz), 2024/09/06
- Re: G-Golf - Callback segmentation fault, David Pirotte, 2024/09/06
- Re: G-Golf - Callback segmentation fault, David Pirotte, 2024/09/06
- Re: G-Golf - Callback segmentation fault, David Pirotte, 2024/09/06
- Re: G-Golf - Callback segmentation fault, pelzflorian (Florian Pelz), 2024/09/07