From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: 53696@debbugs.gnu.org
Subject: bug#53696: Integer overflow on Guix GC size calculation
Date: Wed, 02 Feb 2022 21:04:06 +0100 [thread overview]
Message-ID: <66a344bca9c0ebf7a7430b8af6cd705c93946d7f.camel@gmail.com> (raw)
In-Reply-To: <eiL-NqLXkO8KslOAJSoMQ0KR48Le7DLPP2bE0dw74ydUB3JO5NdKOHVO941JEaGwNVPzaPhHeWEr-If-bxyKovX5DOOav6cpE-_ALeF8F8I=@elenq.tech>
Hi,
Am Mittwoch, dem 02.02.2022 um 19:51 +0000 schrieb Ekaitz Zarraga:
> I mean something like:
>
> 0
> 1
> 2
> 4
> 8
> 10
> 12
> HUGE_NUMBER
> HUGE_NUMBER
> ...
> HUGE_NUMBER
> 15
> 20
> ...
>
> It's like it corrected itself. It happened in "low numbers" (less
> than a
> hundred).
>
> I just say this if it helps in the correction. It's very funny, still
> :3
Thanks, that wasn't clear from your original report. As I hinted at in
my previous message, I think you'd get such results through well-placed
bit flips. I'm not aware of Guix itself intentionally or otherwise
causing those, but bit flips are a problem on any modern hardware and
thus I'm sure such glitches will be encountered.
next prev parent reply other threads:[~2022-02-02 20:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 14:06 bug#53696: Integer overflow on Guix GC size calculation Ekaitz Zarraga
2022-02-01 21:20 ` Liliana Marie Prikler
2022-02-01 21:54 ` Ekaitz Zarraga
2022-02-02 19:45 ` Liliana Marie Prikler
2022-02-02 19:51 ` Ekaitz Zarraga
2022-02-02 20:04 ` Liliana Marie Prikler [this message]
2022-02-02 10:05 ` Maxime Devos
2022-02-02 12:04 ` Bengt Richter
2022-02-02 22:46 ` Bengt Richter
2022-02-08 10:01 ` Ludovic Courtès
2022-02-08 10:52 ` Ekaitz Zarraga
2022-02-10 20:25 ` Ludovic Courtès
2022-02-10 20:27 ` Ekaitz Zarraga
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=66a344bca9c0ebf7a7430b8af6cd705c93946d7f.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=53696@debbugs.gnu.org \
--cc=ekaitz@elenq.tech \
/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).