Re: LYNX-DEV Lynx bug while fetching news group list

[Jason Castonguay]

Hi there.  The less program did the trick, and I captured the last 40
lines or so.  I hope this is far back enough for you to judge where the
error occurred.  Here it is.

_________________________________________________________________

HTParse: aName:news://news.ntplx.net/ausgovdirthe   relatedName:news://news.ntpl
x.net/
1
HTParse: result:news://news.ntplx.net/ausgovdirthe
HTParse: aName:news://news.ntplx.net/ausgovdirthe   relatedName:
HTParse: result:
Entered HTAnchor_findAddress
New anchor 0x862a528 has hash 51 and address `news://news.ntplx.net/ausgovdirthe
'
Linking anchor 0x8629f68 to anchor 0x862a528
HText_endAnchor: number:11350 link_type:1
GridText: split_line called
B dk.erhverv    Erhvervsrelateret stof for forskellige erhvervsgrupper.
GridText: split_line called
new Anchor 0x862a618 named `' is child of 0x81297f0
Entered HTAnchor_findChildAndLink
HTParse: aName:news://news.ntplx.net/dk.erhverv   relatedName:news://news.ntplx.
net/
1
HTParse: result:news://news.ntplx.net/dk.erhverv
HTParse: aName:news://news.ntplx.net/dk.erhverv   relatedName:
HTParse: result:
Entered HTAnchor_findAddress
/dosc/lynx.log line 159279/159308 99%
New anchor 0x862a6b0 has hash 70 and address `news://news.ntplx.net/dk.erhverv'
Linking anchor 0x862a618 to anchor 0x862a6b0
HText_endAnchor: number:11351 link_type:1
GridText: split_line called
B alt.aa.aaa.aaaaaaaaaaaaaaa.aaaa.aa.aaaaa.aaaa.aaaaa.aaa.aaaaa.aa.aa.aa.aaa.bb.
bbb.bbb.bbb.bb.bb.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.b.bb.bbbb.cc
ccccc.cccc.ccc.ccc.cccc.cccc.cccc.cccc.cccc.cc.ccccc.ccc.cc.d.dddd.dddd.ddd.ddd.
dddd.ddd.ddd.dd.dd.ddd.ddddddddd.ddd.ddd.ddd.dd.dd.ddd.ddd.ddd.dd.eeee.eeeeeeee.
eee.eeee.eeee.eeeee.eee.ee.e.eeee.eeeee.eeee.eee.eeee.eee.eee.ffff.fff.ffff.ffff
f.fffff.ffffff.ffffff.fffff.fffffffff.ffffff.fffffff.fffffffff.fffffffff.ffffff.
ffffffff.fffffff.fff.fff.fff.ffff.GridText: split_line called
new Anchor 0x862a500 named `' is child of 0x81297f0
Entered HTAnchor_findChildAndLink
HTParse: aName:news://news.ntplx.net/alt.aa.aaa.aaaaaaaaaaaaaaa.aaaa.aa.aaaaa.aa
aa.aaaaa.aaa.aaaaa.aa.aa.aa.aaa.bb.bbb.bbb.bbb.bb.bb.b.b.b.b.b.b.b.b.b.b.b.b.b.b
.b.b.b.b.b.b.b.b.b.b.b.b.bb.bbbb.ccccccc.cccc.ccc.ccc.cccc.cccc.cccc.cccc.cccc.c
c.ccccc.ccc.cc.d.dddd.dddd.ddd.ddd.dddd.ddd.ddd.dd.dd.ddd.ddddddddd.ddd.ddd.ddd.
dd.dd.ddd.ddd.ddd.dd.eeee.eeeeeeee.eee.eeee.eeee.eeeee.eee.ee.e.eeee.eeeee.eeee.
eee.eeee.eee.eee.ffff.fff.ffff.fffff.fffff.ffffff.ffffff.fffff.fffffffff.ffffff.
fffffff.fffffffff.fffffffff.ffffff.ffffffff.fffffff.fff.fff.fff.ffff.   relatedN
ame:news://news.ntplx.net/
1
HTParse: result:news://news.ntplx.net/alt.aa.aaa.aaaaa

_________________________________________________________________

I tried doing a "where" at the "(gdb)" prompt, but I got nothing more than
I already knew (it just repeated the last line of the contense I sent
earlier).  I hope the trace file helps a bit more.  Thank you.


Jason

On Fri, 14 Nov 1997, Klaus Weide wrote:

> On Fri, 14 Nov 1997, Jason Castonguay wrote:
> 
> > Hi there.  That gdb program is amazing (I never used it before and hadn't
> > realized what it could do).  I couldn't check out the Lynx.trace file
> > because it was too big (159,321 lines).  All my editors had a problem with
> > that <g>.
> > 
> > Here's what gdb reported after issuing the command: "gdb lynx core"
> > 
> > _________________________________________________________________
> > 
> > Core was generated by `lynx -trace news://news.ntplx.net'.
> > Program terminated with signal 11, Segmentation fault.
> > Reading symbols from /lib/libncurses.so.3.0...(no debugging symbols 
> > found)...
> > done.
> > Reading symbols from /lib/libc.so.5...(no debugging symbols found)...done.
> > Reading symbols from /lib/ld-linux.so.1...done.
> > #0  0x6666662e in ?? ()
> > 
> > _________________________________________________________________
> 
> Ok, but you should have typed "where" at the (gdb) prompt, that should be
> more interesting.
> 
> For very large files, like the Lynx.trace: since you use Linux, I am sure
> you have "less".  Try
> 
>    less +G Lynx.trace
> 
> (The +G just makes it jump to the end; you can then page backward and
> forward with 'b' and SPACE.)
>    tail -20 Lynx.trace
> should also give you the last screenful of the file.
> 
> Of course you can also try whether Lynx itself can load such a big file
> :-)  It should be able to, IF you have enough memory.  And it may take a
> while.
> 
> I don't know whether all this will lead to anything; it is not clear from
> what date your "2.7.1F" is.  If the problem persists, I suggest you try
> whether the development code from <URL:http://sol.slcc.edu/lynx/current/>
> has the same problem.
> 
> It is also possible that this isn't a Lynx problem but that you are
> running out of memory; although in that case I would expect an "out
> of memory" message before Lynx quits.
> 
>    Klaus
> 
> 
> 

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;