From: Christopher Baines <mail@cbaines.net>
To: guile-user@gnu.org
Subject: procedures turn to programs and location information lost
Date: Mon, 24 Jun 2024 14:25:25 +0100 [thread overview]
Message-ID: <87ed8m5v7e.fsf@cbaines.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
Hey,
Any ideas why Guile seems to loose track of which procedure is which?
I've got some Guile code to track how long it takes to run some
procedures, so first I see output like:
2024-06-23 19:58:19 warning: delay of 3.380 seconds: #<procedure 7fb59a6dc5b0 at guix-build-coordinator/coordinator.scm:708:4 (_)>
2024-06-23 19:58:19 0.016: #<procedure store-build (derivation-name uuid priority tags #:key skip-updating-other-build-derived-priorities)>
2024-06-23 19:58:19 0.004: #<procedure 7fb56869a9c0 at guix-build-coordinator/datastore/sqlite.scm:1320:3 (db)>
2024-06-23 19:58:19 0.012: #<procedure 7fb568516280 at guix-build-coordinator/datastore/sqlite.scm:4347:6 (db)>
But then after some time of the program running, the output changes to
something like:
2024-06-24 15:18:02 warning: delay of 1.128 seconds: #<program 7fb51102f960 7fb59b183514>
2024-06-24 15:18:02 0.161: #<program 7fb59b1de310 7fb59b19a7d0>
2024-06-24 15:18:02 0.966: #<program 7fb59b1de278 7fb59b19970c>
2024-06-24 15:18:02 0.392: #<program 7fb59b1de260 7fb59b1989d0>
2024-06-24 15:18:02 0.507: #<program 7fb59b1de260 7fb59b1989d0>
So the procedures become programs, and the locations are lost.
I've already disabled JIT to see if that helps, and it doesn't seem
to. Any ideas how I can stop this from happening?
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
reply other threads:[~2024-06-24 13:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ed8m5v7e.fsf@cbaines.net \
--to=mail@cbaines.net \
--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).