Re: G-Golf - Callback segmentation fault
David Pirotte <[email protected]>
| Newsgroups | gmane.lisp.guile.user |
|---|---|
| Message-ID | <20240905182306.77491907@tintin> |
> 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' ...
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEhCJlRZtBM3furJHe83T9k6MFetcFAmbaIToACgkQ83T9k6MF etcFWQf9Fu3LEXbdT6r4GLs8qoagBdpDXg4jl2n9s25nmKQG++E2ubxuFgF6Ydfq zyHF8EI7FTg6OsSqCiox9Sb4TJ0cq7MYE8aE43EkhGrna2GwMIwouIbMCtb8yQQD 9ILF+NLfHcaF/Oz2mYjDkRDuRZF/aTOpq4brgVv24zCbjShJ2QiQ1Rczk3/8nS62 b71tf/kqcydm5rpgBzOQZ+QXLBjKGkFynLPlf0qVoIRekQRzjFU6RakMrTLPUSjS zs8Hsc9SM0TsG7fGW0mbxtBPo0PB1YoYQSqmubqP8PhzIFEu8146oezuSVcuxd69 uYKjDaAf1z72Rkwcg6eU4NuQVeiOQg== =HK+i -----END PGP SIGNATURE-----