Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!caip!princeton!allegra!ulysses!mhuxr!mhuxn!ihnp4!inuxc!pur-ee!uiucdcs!uiucuxc!hamilton
From: hamilton@uiucuxc.CSO.UIUC.EDU
Newsgroups: net.micro.amiga
Subject: CreatePort bug?
Message-ID: <148600113@uiucuxc>
Date: Sun, 3-Aug-86 03:06:00 EDT
Article-I.D.: uiucuxc.148600113
Posted: Sun Aug  3 03:06:00 1986
Date-Received: Thu, 14-Aug-86 21:59:47 EDT
Lines: 20
Nf-ID: #N:uiucuxc:148600113:000:954
Nf-From: uiucuxc.CSO.UIUC.EDU!hamilton    Aug  3 02:06:00 1986


the version of CreatePort() listed in appendix F (p3) of the 1.1 RKM
(and the one that came with aztec 3.20a) performs a NewList() on the
mp_MsgList structure _only if 'name' is NULL_.  that doesn't look right
to me, so i promptly deleted the "else".

i haven't verified it, but i strongly suspect that adding messages to
(and later removing them from) an uninitialized (ie, all zero) MsgList
can produce crashes.  when a message is added to such a List, won't
the longwords at locations 0 and 4 be treated as the link pointers of
a Node?  and everybody expects location 4 to point to execbase...

however, i see people using named ports all the time, with apparently
no problems.  have i jumped to conclusions?

	wayne hamilton
	U of Il and US Army Corps of Engineers CERL
UUCP:	{ihnp4,pur-ee,convex}!uiucdcs!uiucuxc!hamilton
ARPA:	hamilton%uiucuxc@a.cs.uiuc.edu	USMail:	Box 476, Urbana, IL 61801
CSNET:	hamilton%uiucuxc@uiuc.csnet	Phone:	(217)333-8703