Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!dciem!nrcaer!cognos!brianc
From: brianc@cognos.uucp (Brian Campbell)
Newsgroups: comp.os.minix
Subject: asld bug?
Message-ID: <1237@cognos.UUCP>
Date: Mon, 10-Aug-87 13:50:38 EDT
Article-I.D.: cognos.1237
Posted: Mon Aug 10 13:50:38 1987
Date-Received: Wed, 12-Aug-87 05:37:17 EDT
Organization: Cognos Incorporated, Ottawa, Canada
Lines: 23


   Does asld  enforce any restrictions on  the size of the  text or data
segments? I was  trying to get filecomp (from the  Turbo C distribution)
to compile under minix and couldn't understand why it kept blowing up on
me. I finally  did a `size filecomp`  and found that the bss  area had a
negative size!  How come  asld (or even  cc -- it  was one  large array)
didn't catch this?

   Also, I finally  tracked down my last problem with  less under minix.
It involved  a clash between  putc() as defined  in less and  the libc.a
version.  sprintf() calls  putc()  to output  characters  in the  format
string,  but the  putc() that  got used  was less's  which messed  up my
prompt string.

   Is it really  all that unusual that  for a program to  define its own
putc() that it is acceptable for  sprintf() [and who knows what else] to
break in  the process?  And while I'm here  ... I thought  sprintf() was
supposed to return the number of characters copied... not the address of
the buffer.
-- 
Brian Campbell          uucp: decvax!utzoo!dciem!nrcaer!cognos!brianc
Cognos Incorporated     mail: 3755 Riverside Drive, Ottawa, Ontario, K1G 3N3
(613) 738-1440          fido: sysop@163/8