3 ms·
This should have been the clue: > The call to fork() did check for a -1 and handled it as an error and bailed out. So how was it somehow surviving all the way
by tantalor 2y ago
This should have been the clue:
> The call to fork() did check for a -1 and handled it as an error and bailed out. So how was it somehow surviving all the way down to where kill() was called?
If the source code doesn't match the observed behavior, you should suspect the code changed.
- yuliyp 2y agoEventually she got there. There were a lot of other possibilities: maybe there's another place where kill is called; maybe the `kill` hypothesis is wrong; maybe something weirder is happening. Getting back to "oh maybe that's not what the code looked like back then" would likely take some further time.