[COFF] Conditions, AKA exceptions.

Larry McVoy lm at mcvoy.com
Mon Mar 13 02:53:19 AEST 2023


On Sun, Mar 12, 2023 at 12:46:40PM -0400, Paul Winalski wrote:
> On 3/12/23, Ralph Corderoy <ralph at inputplus.co.uk> 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

	panic(psig)

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


More information about the COFF mailing list