From: Matija Obid <matija.obid@posteo.net>
To: David Pirotte <david@altosw.be>
Cc: guile-user@gnu.org
Subject: Re: G-Golf - Callback segmentation fault
Date: Sat, 31 Aug 2024 16:35:07 +0000 [thread overview]
Message-ID: <87cylo8xc4.fsf@posteo.net> (raw)
In-Reply-To: <20240828211805.68f594a7@tintin> (David Pirotte's message of "Wed, 28 Aug 2024 21:18:05 -0300")
Hello David,
> So your patch seems to point to a problem in the upstream definition of
> the (most recent) g-callable-info-create-closure, which is the one
> everybody who's using GI >= 1.71.0 should use ...
I see. The comment in deprecated function made me thinking and I found
notice in LFS [1]:
> --disable-exec-static-tramp
> Disable static trampoline support. It's a new security feature in
> libffi, but some BLFS packages (notably GJS and
> gobject-introspection) have not been adapted for it.
This flag was recently removed [2] in nixpkgs with a comment:
> The fix for gobject-introspection is in version 1.72.
Bottom line: If I compile Guile with patched libffi [3] dependency
(where flag "disable-exec-static-tramp" is present) problematic examples
are working (without patched G-Golf).
> Do you (or anyone else interested ofc) have an idea of why would
> g-callable-info-create-closure perfectly create a closure pointer on
> debian, and not on guix/nix? Here is the upstream code def [2]
Most probably has Debian present flag "disable-exec-static-tramp" when
configuring libffi. Where can we check that?
I still wonder where is the problem, in Guile, G-Golf or
gobject-introspection (which according to [2] should not be a problem).
[1] https://www.linuxfromscratch.org/~xry111/lfs-cross-la/view/systemd/chapter08/libffi.html
[2] https://github.com/NixOS/nixpkgs/pull/257742
[3] Libffi is used in a lot of packages. I patch it only for Guile.
--
Regards,
Matija
next prev parent reply other threads:[~2024-08-31 16:35 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 [this message]
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
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=87cylo8xc4.fsf@posteo.net \
--to=matija.obid@posteo.net \
--cc=david@altosw.be \
--cc=guile-user@gnu.org \
/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).