lynx-dev Re: "new anchor" message

[Klaus Weide]

On Tue, 2 Feb 1999, Clair Wilson wrote:

> Does "new anchor" have anything to do with the problem ?
> 
> We have one rs6000 upon which lynx is functional. I traced lynx there in
> order to look for trace differences.

Are you really comparing the same versions?

> I don't see the "new anchor" message coming out on the lynx which is
> functioning properly. However, it comes out every time on the lynx which
> is failing. So here is the "new anchor" message.

If one is an old version, the trace output may have changed.
I don't think this is significant.

Actually the trace *should* say "New anchor ..." if this is on
startup, as it does.  There's nothing wrong with that.
The later, different status number you pointed to is just a
result of something failing earlier, it has no direct relation
to sytem error numbers.

I don't really trust that your method of capturing trace output
is reliable.  The 2.8 should direct trace output by default int
a file Lynx.trace, that should be more reliable than cut-and-pase
from the screen.  (If you don't get the file, try the -tlog flag).

We are getting further away from where the problem most likely
lies.  Thanks for the traces, but unfortunately they only show
that they don't show enough.  Lynx probably isn't really generating
enough trace output to pinpoint the problem.

I asked you a number of question in another mail which you didn't answer -
please do so.  Most important - Did you compile Lynx yourself, can you
recompile it?  Also, do you have a system call trace utility, like strace
or truss on other Unixes?

   Klaus