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: Sun, 5 May 2024 18:30:52 -0300 [thread overview]
Message-ID: <20240505183052.2e616223@tintin> (raw)
In-Reply-To: <8734qx2fv1.fsf@pelzflorian.de>
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
Hi Florian,
> (gc-disable) was a smart idea, sadly it does not help, but at least
> we know now. ...
I am not entirely convinced yet - in one way or another, somewhere,,
somehow, the klass->snapshot is 'corrupted', either the pointer, or the
mem it points to ... why, when, where ... ?
> scheme@(guile-user)> ,use (g-golf)
> scheme@(guile-user)> (gc-disable)
> scheme@(guile-user)> (chdir "/home/florian/src/g-golf/examples/gtk-4")
> scheme@(guile-user)> (load "drawing-widget.scm")
> scheme@(guile-user)> (main '("-d"))
> ...
Thanks for the valgrind session info, but could you kindely 'reproduce'
the gdb full backtrace and run the few gdb command as in the previous
email, so i can compare ...
Thanks,
David
> > Imo, you should locally patch your guix image so it has one
> > gdk-pixbuf lib installed keep the one that has the debug symbols
>
> The one gdk-pixbuf problem is locally solved.
And yet, i would like you to locally fix this 'proper', is this
possible? If so, could you do that, thanks.
> Well the d-bus service cannot be a requirement of a Guix package. It
> could be a requirement of a Guix service, but g-golf is not a service
> but just a package.
I never said nor asked you to fix this problem 'in g-golf' :) -
But could you manually start the service, and re-run the above,
thanks
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-05-05 21:30 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)
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 [this message]
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=20240505183052.2e616223@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).