From: David Pirotte <david@altosw.be>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: GNU G-Golf 0.8.0-rc-3 available for testing
Date: Sat, 4 May 2024 02:59:29 -0300 [thread overview]
Message-ID: <20240504025929.1368a279@tintin> (raw)
In-Reply-To: <87h6ffgmb6.fsf@pelzflorian.de>
[-- Attachment #1: Type: text/plain, Size: 2250 bytes --]
Hi Florian,
> > The true error location was given by the gdb backtrace, the
> > gtk-widget-snapshot-child call, presumably with a bad pointer or so
> > ...
> Hmm my assumption was that all callbacks are broken, not vfuncs
> specifically ...
Very unlikely, but the important thing is to get a proper full
backtrace, as then there is no need to make assumptions ...
> The GTK_A11Y warning I can easily fix by exporting GTK_A11Y=none, but
> it was interesting that the crash happens two function calls away from
> where the warning is printed.
I can't make any useful deduction from the above, a warning is expected
here, till you (the guix team) fix it, let's set this env var, and
concentrate on the cause of the segfault ...
> On a x86_64 GNOME laptop on the distro Guix System on the g-golf devel
> branch with (main '("guile" "--debug")):
> ;;;
this gdb backtrace 'preamble' is, to me, useless as well
> On my aarch64 rock64 the complete backtrace is useless:
> (gdb) bt
> #0 0x0000ffff8066e278 in ?? ()
> #1 0x000000001b976640 in ?? ()
I won't be able to help you help Guix track this problem unless we get a
useful backtrace, so much as because i probably will need it to ask for
some help from upstream devs ...
Could you ask for some help from guix to produce it?
> Your next e-mail:
> I get only
>
> scheme@(guile-user)> (main '("guile" "--debug"))
> ;; g-application-run
> ;; application: #<<gtk-application> 7fce23e673b0>
> ;; argc: 0
> ;; argv: ()
> ;; gtk-window-set-child
> ;; window: #<<gtk-application-window> 7fce23e730c0>
> ;; child: #<<drawing-widget> 7fce23e7bd10>
> ;; gtk-window-present
> ;; window: #<<gtk-application-window> 7fce23e730c0>
Yes, i did expect this and wanted to show you ... you don't see
any g-golf trace here because it fails in the gtk engine, as i
understood so far, before it can't find the derived class snapshot
vfunc.
David
ps: you did not answer my quiz about your guix host distro - i
would like you to - at least temporarily - manually install g-golf
there and see if everything works fine ... Could you do that? thanks
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-05-04 5:59 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 [this message]
2024-05-04 14:31 ` pelzflorian (Florian Pelz)
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=20240504025929.1368a279@tintin \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).