From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46212@debbugs.gnu.org
Subject: bug#46212: ci.guix.gnu.org narinfos with excessive NarSize
Date: Wed, 24 Feb 2021 11:26:27 +0100 [thread overview]
Message-ID: <87blc9oj70.fsf@gnu.org> (raw)
In-Reply-To: <87a6rwb6go.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 22 Feb 2021 14:03:03 +0100")
Hey,
> The bug here is likely due to 32-bit signed integer wrapping. That can
> only happen in C code, so to me possible culprits would be
> guile-simple-zmq or the layer above it (if there’s a binary protocol
> involved) or the postgresql interface. Only a vague intuition, though.
Hmm, looks like you're right! There's a memory corruption in the
remote-server process that's really hard to reproduce. I suspect the ZMQ
library or its Guile bindings.
I'm trying to valgrind the process to identify the issue, without much
success for now.
Thanks,
Mathieu
next prev parent reply other threads:[~2021-02-24 10:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 14:47 bug#46212: ci.guix.gnu.org narinfos with excessive NarSize Christopher Baines
2021-01-31 15:20 ` Ludovic Courtès
2021-02-01 9:15 ` Ludovic Courtès
2021-02-19 15:11 ` Ludovic Courtès
2021-02-22 8:59 ` Mathieu Othacehe
2021-02-22 13:03 ` Ludovic Courtès
2021-02-24 10:26 ` Mathieu Othacehe [this message]
2021-02-01 19:57 ` Christopher Baines
2021-02-02 21:48 ` Ludovic Courtès
2021-03-21 14:38 ` Ludovic Courtès
2021-03-21 14:55 ` Ludovic Courtès
2021-03-21 14:55 ` Ludovic Courtès
2021-03-29 7:45 ` Mathieu Othacehe
2021-04-07 9:09 ` Brendan Tildesley via Bug reports for GNU Guix
2021-06-11 12:04 ` Christopher Baines
2021-06-18 9:48 ` Ludovic Courtès
2021-11-24 23:28 ` Ludovic Courtès
2021-11-25 8:42 ` Christopher Baines
2021-11-26 10:11 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blc9oj70.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=46212@debbugs.gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).