Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!bellcore-2!bellcore!bae!aw
From: aw@bae.bae.bellcore.com (Andrew Wason)
Newsgroups: comp.windows.x
Subject: Re: Is you xrn6.13 crashing too?
Message-ID: <28297@bellcore.bellcore.com>
Date: 29 Oct 90 15:32:02 GMT
References: <477@grapevine.EBay.Sun.COM>
Sender: news@bellcore.bellcore.com
Reply-To: aw@cellar.bae.bellcore.com
Organization: Bell Communications Research
Lines: 29

In article <477@grapevine.EBay.Sun.COM>, gcmcnutt@mlsgcm.Ebay.sun.COM (Greg McNutt) writes:
> We have been fighting a problem with the latest versions of
> xrn and libXt.  It appears that our upgrade from xrn6.10 to
> xrn6.13 (or even xrn6.11) now core dumps at an interesting
> place.
> 
> We are using MIT's libXt for this test (patched to fix-18).

I have a similar problem with xrn 6.13 on a Pyramid.
I don't think our MIT libXt has had any of the fixes applied.

> The crash appears on the *third* entry into the article read
> mode.  We have traced back the failure to the *third* entry
> back into the newgroup mode i.e.:
> 
> run xrn (ng mode) -> read -> ng -> read -> ng

With me, it's not so consistent. It sometimes happens when entering read mode.
A dialog box pops up saying signal 11 was caught. Sometimes it takes
quite a while before it happens, if at all.

I have also built xrn 6.13 on a Sun4 and it has no problems.

Andrew

--------------------------------------------------------------------------------
Andrew Wason                                        Bell Communications Research
aw@cellar.bae.bellcore.com                          Piscataway, NJ
bellcore!cellar!aw