jeremy@lana.prime.com (Jeremy Nussbaum) (07/14/89)
I just bought up gnu emacs 18.54 (and 18.53) on an sgi 4d workstation under release 3.1 of the sgi os. I had been using 18.51, compiled on an earlier release of the os. Under 18.51, gnus started up w/o trouble. Now, as soon as it tries to connect to the nntp server it gets a segmentation violation. The traceback shows index.index called by res_init.res_init called by res_search called by _gethostbyname_named called by gethostbyname called by Fopen_network_stream. I have verified that I am still calling gethostbyname with the same valid hostname, and that a small program can make the call successfully. I don't actually have the named up and running. Any ideas on what might be causing the segmentation violation, and what I might do to get around the problem? Thanks in advance, -- Jeremy Nussbaum (jeremy@jeremy.prime.com, ...!harvard!prmcad!jeremy) Prime Computer/2 Crosby Drive MS 16-2 /Bedford, Ma. 01730 (617)275-1800 x6745 Standard Disclaimer: The opinions expressed are mine and not my employer's.
jeremy@lana.prime.com (Jeremy Nussbaum) (07/14/89)
In article <JEREMY.89Jul13160834@lana.prime.com> jeremy@lana.prime.com (Jeremy Nussbaum) writes:
Summary: gethostbyname problem under gnuemacs 18.53/4 with irix 3.1
Date: 13 Jul 89 20:08:34 GMT
Lines: 18
Xref: cvbnet2 comp.sys.sgi:1051 gnu.emacs:109 comp.emacs:5879
I just bought up gnu emacs 18.54 (and 18.53) on an sgi 4d workstation
under release 3.1 of the sgi os. I had been using 18.51, compiled
on an earlier release of the os. Under 18.51, gnus started up w/o trouble.
Now, as soon as it tries to connect to the nntp server it gets a
segmentation violation. The traceback shows index.index called by
res_init.res_init called by res_search called by _gethostbyname_named
called by gethostbyname called by Fopen_network_stream. I have verified
that I am still calling gethostbyname with the same valid hostname, and
that a small program can make the call successfully. I don't actually
have the named up and running. Any ideas on what might be causing the
segmentation violation, and what I might do to get around the problem?
Thanks in advance,
--
Jeremy Nussbaum (jeremy@jeremy.prime.com, ...!harvard!prmcad!jeremy)
OK, I worked on it some more, and finally figured out that it is the
programmers workbench library that is causing the problem. I haven't yet
ascertained which routine is being redefined, but I have "successfully"
gotten a three line program to dump core consistenly simply by linking in the
libPW library. Followups to comp.sys.sgi.
--
Jeremy Nussbaum
jeremy@jeremy.prime.com, ...!harvard!prmcad!jeremy
Prime Computer
2 Crosby Drive MS 16-2
Bedford, Ma. 01730
(617)275-1800 x6745