Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!ncar!noao!ut-sally!blitz!bunda
From: bunda@blitz.cs.utexas.edu (John Bunda)
Newsgroups: comp.os.minix
Subject: hang in test5 (was Re: V1.3 posting # 15 - test1.c and test3.c)
Summary: but that change appears to be in 1.2...
Message-ID: <12207@ut-sally.UUCP>
Date: 29 Jun 88 05:11:10 GMT
Sender: news@ut-sally.UUCP
Lines: 15

In article <385@csed-47.csed-1.IDA.ORG>, roskos@csed-1.IDA.ORG (Eric Roskos) writes:
> > Test 5 would hang and never come back.
...
> I remember correctly, it is because line 6706 uses m_sig.PROC_NR (which is
> field m2_i2) and line 3156 uses m_ptr->CLOCK_PROC_NR, which is field
> m6_i1.  This caused all alarm signals to get sent to the wrong process.

i went to edit the source for signal.c, and guess what---
my version of 1.2 has the change you are suggesting in it!  i am running
the vanilla 1.2 mm binary (i haven't rebuilt it).  is it possible that
the distributed binary is actually not built from the distributed source...
nah, could never happen, right? ;-)  i'm not sure what this means...

-john bunda
 ut cs dept.