Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site luke.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!hao!hplabs!oliveb!bene!luke!sml From: sml@luke.UUCP (Steven List @ Uncle Bene's Farm) Newsgroups: net.news.b Subject: Signal Handling in News Software Message-ID: <186@luke.UUCP> Date: Mon, 3-Jun-85 20:30:16 EDT Article-I.D.: luke.186 Posted: Mon Jun 3 20:30:16 1985 Date-Received: Fri, 7-Jun-85 03:30:44 EDT Distribution: net Organization: Benetics Corp, Mt.View, CA Lines: 25 In installing the news software (readnews, et al), my first experience with it was continuous core dumps. Investigation revealed that there was a conflict between a global variable and a library function. We are running Plexus' version of System III. The `signal' library function invokes subfunction `sigtrap' to establish the signal handling. This is undocumented and dangerous. There is a global used throughout the news software named... `sigtrap'! A simple change of `sigtrap' to `trapsig' throughout the news software eliminated this problem. A second set of core dumps occurred when using readnews. Periodically the SYSBUF buffer would OVERFLOW! Rather than spend a lot of time figuring out why it was overflowing into the next buffer (rcline), I just doubled the size of the buffer. Could there be some inconsistency in the buffered I/O library routines? SYSBUF is the buffer `setbuf'ed for use with stdout. The problem would apparently occur when an article was less than 16 lines but greater than 512 bytes. /-\ :-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-: : Steven List @ Benetics Corporation : : (415) 940-6300 : : {cdp,idi,oliveb,tolerant}!bene!luke!steven : :-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-: \-/