From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: David Pirotte <david@altosw.be>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: GNU G-Golf 0.8.0-rc-3 available for testing
Date: Sat, 04 May 2024 16:31:41 +0200 [thread overview]
Message-ID: <878r0plkc2.fsf@pelzflorian.de> (raw)
In-Reply-To: <20240504025929.1368a279@tintin> (David Pirotte's message of "Sat, 4 May 2024 02:59:29 -0300")
Hi David, thank you for your continuing responses. I will try to get a
backtrace with GTK debug symbols by patching Guix to add a debug output
to GTK, in the hope that I patch the right GTK.
However, my believe is that the error is in G-Golf
closures/callbacks/vfuncs (even though the hl-api tests do pass when run
by Guix build or manually), specifically when I run valgrind on guile
where I load and run drawing-widget.scm, it only shows errors from Boehm
GC (at least mostly false-positive) and from creating threads, but no
errors from GTK. In particular there are errors in scm_c_make_vector,
probably false positive, but I will look at bytevectors this weekend now
(occurrences of bv in g-golf code).
I cannot tell you my host distro because there is none (there could be a
foreign distro, but I have none). It is Guix System, that is Guix all
the way down.
To build G-Golf manually, I can and had patched the its g-golf/init.scm
to use /gnu/store/xxxxxxx/lib/libgirepository-1.0.so file names like the
guile-g-golf package at
<https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/guile-xyz.scm>
does, but it will not be useful.
Setting the GTK_A11Y env var does not make a difference (except the
warning is gone) and on my x86_64 GNOME setup there never is a warning
(although GTK_A11Y is unset, but d-bus is there).
Regards,
Florian
next prev parent reply other threads:[~2024-05-04 14:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 5:56 GNU G-Golf 0.8.0-rc-3 available for testing David Pirotte
2024-04-17 22:30 ` pelzflorian (Florian Pelz)
2024-04-18 22:21 ` David Pirotte
2024-04-19 17:00 ` pelzflorian (Florian Pelz)
2024-04-20 4:51 ` David Pirotte
2024-04-20 8:35 ` pelzflorian (Florian Pelz)
2024-04-30 17:51 ` pelzflorian (Florian Pelz)
2024-05-01 0:51 ` David Pirotte
2024-05-01 8:17 ` pelzflorian (Florian Pelz)
2024-05-07 1:39 ` David Pirotte
2024-05-07 9:36 ` pelzflorian (Florian Pelz)
2024-05-07 23:53 ` David Pirotte
2024-05-08 10:49 ` pelzflorian (Florian Pelz)
2024-05-08 21:51 ` David Pirotte
2024-05-02 18:50 ` pelzflorian (Florian Pelz)
2024-05-02 21:57 ` David Pirotte
2024-05-03 5:00 ` David Pirotte
2024-05-03 11:35 ` pelzflorian (Florian Pelz)
2024-05-04 5:59 ` David Pirotte
2024-05-04 14:31 ` pelzflorian (Florian Pelz) [this message]
2024-05-04 18:08 ` pelzflorian (Florian Pelz)
2024-05-04 22:11 ` David Pirotte
2024-05-04 22:23 ` David Pirotte
2024-05-04 21:39 ` David Pirotte
2024-05-05 1:43 ` pelzflorian (Florian Pelz)
2024-05-05 21:30 ` David Pirotte
2024-05-06 9:45 ` pelzflorian (Florian Pelz)
2024-05-06 9:53 ` Basile Starynkevitch
2024-05-06 13:08 ` pelzflorian (Florian Pelz)
2024-05-03 0:17 ` David Pirotte
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=878r0plkc2.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--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).