Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!ugle.unit.no!nuug!ifi!enag From: enag@ifi.uio.no (Erik Naggum) Newsgroups: comp.unix.questions Subject: Re: Signals and dbx Message-ID: Date: 6 Feb 91 07:39:55 GMT References: <6992@alpha.cam.nist.gov> <15091@smoke.brl.mil> Sender: enag@ifi.uio.no (Erik Naggum) Organization: Naggum Software, Oslo, Norway Lines: 19 In-Reply-To: gwyn@smoke.brl.mil's message of 5 Feb 91 20:45:18 GMT In article <15091@smoke.brl.mil>, Doug Gwyn writes: In article <6992@alpha.cam.nist.gov>, Sean Sheridan Coleman X5672 writes: >Does ^D produce a signal ? Not under normal circumstances. Usually that character is used to delimit chunks of input text; whatever has been typed (in canonicalizing mode) up to the so-called EOF character is made available for reading and the EOF character is discarded. No signal is involved. Perhaps the special case that makes people believe that ^D is more special than it is should be elaborated upon. When you have _not_ typed anything before the so-called EOF character, the read(2) system call returns the number of characters read, which is 0. Recall that 0 from read(2) is the canonical End Of File indication, unless other provisions have been made (such as O_NDELAY). -- [Erik Naggum] Naggum Software, Oslo, Norway