unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
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: Tue, 27 Aug 2024 20:09:29 +0000	[thread overview]
Message-ID: <87a5gxybgm.fsf@posteo.net> (raw)
In-Reply-To: <20240821212129.7647d035@tintin> (David Pirotte's message of "Wed, 21 Aug 2024 21:21:29 -0300")

[-- Attachment #1: Type: text/plain, Size: 272 bytes --]

Hello again,

I think I found something.

There is a version check in "g-callable-info-make-closure" function, if
I disable it (check patch) all examples works just fine.

I'm not quite sure what these functions does, can you take another look?

My gi version is 1.80.1.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fixing-callbacks-segfaults.patch --]
[-- Type: text/x-patch, Size: 845 bytes --]

From 4bec7836f17dfd453b877f65d5e91aa29c082d70 Mon Sep 17 00:00:00 2001
From: Matija Obid <matija.obid@posteo.net>
Date: Tue, 27 Aug 2024 21:34:50 +0200
Subject: [PATCH] Fixing callbacks segfaults

---
 g-golf/hl-api/callback.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/g-golf/hl-api/callback.scm b/g-golf/hl-api/callback.scm
index 633635c..04b9ea2 100644
--- a/g-golf/hl-api/callback.scm
+++ b/g-golf/hl-api/callback.scm
@@ -150,7 +150,7 @@
                                       ffi-cif
                                       ffi-closure-callback
                                       user-data)
-  (if (gi-check-version 1 71 0)
+  (if (and #f (gi-check-version 1 71 0))
       (g-callable-info-create-closure
        info ffi-cif ffi-closure-callback user-data)
       (g-callable-info-prepare-closure
-- 
2.45.2


[-- Attachment #3: Type: text/plain, Size: 21 bytes --]


-- 
Regards,
Matija

  reply	other threads:[~2024-08-27 20:09 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 [this message]
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
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=87a5gxybgm.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).