From: Larry McVoy <email@example.com>
To: Paul Winalski <firstname.lastname@example.org>
Subject: [COFF] Re: Conditions, AKA exceptions.
Date: Sun, 12 Mar 2023 09:53:19 -0700 [thread overview]
Message-ID: <20230312165319.GN9225@mcvoy.com> (raw)
On Sun, Mar 12, 2023 at 12:46:40PM -0400, Paul Winalski wrote:
> On 3/12/23, Ralph Corderoy <email@example.com> wrote:
> > Do you ever find things are so messed up that stdio has trouble whereas
> > using write(2) with compile-time memory allocations for a buffer would
> > have a better chance of reaching the TTY?
> I hate it when that happens. Even worse is when adding the write(2)
> with compile-time memory allocations makes the bug go away. I once
> had to spend three days camped out in someone's office debugging a
> compiler crash. The crash only happened 4 hours into a massive
> multi-file compilation, and this guy's login session was the only one
> where the problem reproduced under the debugger. Heisenbugs are hell.
I had one like that. Sometimes, rarely, suninstall would throw a
which meant that someone in the kernel had messed with the process'
signal mask, which is a no-no.
Turns out that the SCSI twins had heard that people were interrupting
suninstall if it took too long, so under certain conditions, the SCSI
tape driver would disable SIGINT.
It was (obviously) my fault because I was doing POSIX conformance and
I was the last person in many kernel files.
Took me a long time to track that one down.
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2023-03-12 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:11 [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Bakul Shah
2023-03-10 17:28 ` segaloco via COFF
2023-03-10 17:34 ` Larry McVoy
2023-03-10 17:35 ` Bakul Shah
2023-03-10 17:42 ` Larry McVoy
2023-03-11 11:28 ` [COFF] Conditions, AKA exceptions Ralph Corderoy
2023-03-12 4:23 ` [COFF] " Theodore Ts'o
2023-03-12 10:44 ` Ralph Corderoy
2023-03-12 16:46 ` Paul Winalski
2023-03-12 16:53 ` Larry McVoy [this message]
2023-03-10 17:43 ` [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) segaloco via COFF
2023-03-10 18:03 ` Dan Cross
2023-03-10 18:57 ` Bakul Shah
2023-03-10 19:57 ` Marshall Conover
2023-03-13 16:47 ` [COFF] Conditions, AKA exceptions Ralph Corderoy
2023-03-13 17:10 ` [COFF] " Paul Winalski
2023-03-13 21:12 ` Dave Horsfall
2023-03-10 17:47 ` [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Bakul Shah
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 NNTP newsgroup(s).