Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucla-cs.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!talcott!panda!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!trwrb!trwrba!cepu!ucla-cs!ekrell
From: ekrell@ucla-cs.UUCP
Newsgroups: net.news
Subject: Re: rn adding newsgroups
Message-ID: <5815@ucla-cs.ARPA>
Date: Mon, 3-Jun-85 23:22:48 EDT
Article-I.D.: ucla-cs.5815
Posted: Mon Jun  3 23:22:48 1985
Date-Received: Fri, 7-Jun-85 03:39:11 EDT
References: <303@cuae2.UUCP>
Reply-To: ekrell@ucla-cs.ARPA (Eduardo Krell)
Organization: UCLA Computer Science Department
Lines: 18
Summary: 

In article <303@cuae2.UUCP> netnews@cuae2.UUCP (Netnews Admin) writes:
>I have seen numerous occasions where rn 4.3 will dump core with
>SIGSEGV while or just after adding new newsgroups and using "L"
>and a number to specify the location of the addition.  A stack
>trace from sdb follows.  Has anybody else seen this?  We are
>running SVR2 on an AT&T 3B2.  Thanks.

  I have seen a lot of rn crashes due to SIGSEGVs with the old rn.
I haven't seen any crash since I installed rn 4.3. The crashes were all on
a call to malloc (probably due to some string allocated via malloc being
overwritten and garbling the pointers malloc() and free() use).
  I was never able to pinpoint the problem since by the time it core dumped
it was too late (the actual error happened much sooner).
  It frequently crashed when using the "K" command. It would say "Badly
compiled pattern" and coredump.
-- 
    Eduardo Krell               UCLA Computer Science Department
    ekrell@ucla-locus.arpa      ..!{sdcrdcf,ihnp4,trwspp,ucbvax}!ucla-cs!ekrell