From: Nate Eldredge <nate@thatsmathematics.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cat a binary = system crash?
Date: Thu, 8 May 2025 20:21:52 -0600 [thread overview]
Message-ID: <863B1956-DDB7-4E5D-A73F-672A8928DC3E@thatsmathematics.com> (raw)
In-Reply-To: <CAHqckJ0qyRVabD99inyKN8vqVB-jSEA6A4k7Bqd9bHo4G2RpRg@mail.gmail.com>
> On May 8, 2025, at 20:12, Mitchell Dorrell <mwd@psc.edu> wrote:
>
> This is not a bug report and I'm not really seeking assistance, I'm just
> inviting discussion because... this shouldn't be able to happen, right?
Right.
Unless you can reproduce it, I don't think we can reject the "null hypothesis" that the crash was caused by something unrelated (e.g. hardware problem) that just coincidentally happened to occur during this particular task.
next prev parent reply other threads:[~2025-05-09 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 2:12 [gentoo-user] Cat a binary = system crash? Mitchell Dorrell
2025-05-09 2:21 ` Nate Eldredge [this message]
2025-05-09 2:57 ` Eli Schwartz
2025-05-09 4:44 ` Mitchell Dorrell
2025-05-14 2:40 ` Mitchell Dorrell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=863B1956-DDB7-4E5D-A73F-672A8928DC3E@thatsmathematics.com \
--to=nate@thatsmathematics.com \
--cc=gentoo-user@lists.gentoo.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