Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!bu.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!mucs!cns!umaida!jf
From: jf@ap.co.umist.ac.uk (John Forrest)
Newsgroups: comp.mail.sendmail
Subject: Re: Sendmailv5.65+IDA problem
Message-ID: <1990Nov15.110911@ap.co.umist.ac.uk>
Date: 15 Nov 90 11:09:11 GMT
References: <1990Nov13.173733@ap.co.umist.ac.uk> <1990Nov14.215011.4610@comp.vuw.ac.nz>
Sender: usenet@cns.umist.ac.uk (News System)
Reply-To: jf@ap.co.umist.ac.uk (John Forrest)
Organization: UMIST Computation, Manchester, UK.
Lines: 29

In article <1990Nov14.215011.4610@comp.vuw.ac.nz>, Andy.Linton@comp.vuw.ac.nz (Andy Linton) writes:
|> 
|> This could be the same problem that I came against and posted details of
|> a few days ago. On our MOREbsd HP boxes there is/was a bug in routine
|> doprnt() which is called by printf() and co. The bug is exercise by the
|> new version of putline() in util.c
|> 
|> You can check whether this bug is present in your doprnt() routine by
|> the following:
|> 
|> #include <stdio.h>
|> 
|> main()
|> {
|> 	printf("doprnt() is %.0scorrect\n", "NOT ");
|> }
|> 
|> The old version of putline() could be used to further check for the
|> prescence of this bug.

This has indeed turned out to be the problem. The old 5.61 putline works fine on
our Apollo system, the new one does not. I'm not sure why it has changed, anyway
- on a cursorary glance, the expected behaviour seems identical, and I don't
believe the new complicated printf's are necessarily more efficient than the
previous fputs calls.

John Forrest
Dept of Computation
UMIST.