Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!brunix!cgy From: cgy@cs.brown.edu (Curtis Yarvin) Newsgroups: comp.unix.programmer Subject: Re: List of routines safe to use in signals? Message-ID: <59190@brunix.UUCP> Date: 12 Dec 90 04:47:29 GMT References: <1960@necisa.ho.necisa.oz> Sender: news@brunix.UUCP Reply-To: cgy@cs.brown.edu (Curtis Yarvin) Organization: Brown University Department of Computer Science Lines: 22 In article <1960@necisa.ho.necisa.oz> boyd@necisa.ho.necisa.oz (Boyd Roberts) writes: >In article rang@cs.wisc.edu (Anton Rang) writes: >> >> Anyway, is such a list available on the net somewhere? Lacking >>that, is there a reasonable heuristic to guess what's safe? > >Assume that nothing is safe when it comes to library routines >being called from within signal handlers. There should be a >FAQ entry that encourages the practice of doing as little >as possible in signal handlers. Hey, excuse me if I'm being a complete newbie. But how can a reentrant library routine, say "strcpy", cause problems in this case? >Boyd Roberts boyd@necisa.ho.necisa.oz.au >``When the going gets weird, the weird turn pro...'' Curtis "I tried living in the real world Instead of a shell But I was bored before I even began." - The Smiths