Re: [Lynx-dev] junk pointer

[Thomas Dickey]

On Thu, 30 Dec 2004, Stef Caunter wrote:

> Haven't seen this before. Built dev9 --with-ssl, --enable-file-upload.
>
> I guess this is platform specific, but stderr (see below) appears in the
> displayed text for http://nfl.com, http://nba.com, http://msn.com.
>
> my lynx -version:
>
> Lynx Version 2.8.6dev.9 (30 Dec 2004)
> libwww-FM 2.14, SSL-MM 1.4.1, OpenSSL 0.9.7-beta3, ncurses 5.2.20010224
> Built on openbsd3.3 Dec 30 2004 14:14:16

Now that my nose is being rubbed in it, that appears to be the same
problem as reported earlier today.  Here's what valgrind tells me about
the first page:

==6922==    at 0x1B907460: free (vg_replace_malloc.c:153)
==6922==    by 0x8115777: HTSACopy (in /usr/local/bin/lynx)
==6922==    by 0x808AA4C: LYCheckForProxyURL (in /usr/local/bin/lynx)
==6922==    by 0x808ADFC: is_url (in /usr/local/bin/lynx)
==6922==    by 0x80D617A: LYLegitimizeHREF (in /usr/local/bin/lynx)
==6922==    by 0x80B2616: HTML_start_element (in /usr/local/bin/lynx)
==6922==    by 0x81101CE: start_element (in /usr/local/bin/lynx)
==6922==    by 0x810D9D6: SGML_character (in /usr/local/bin/lynx)
==6922==    by 0x8102E83: SGML_write (in /usr/local/bin/lynx)
==6922==    by 0x80C58F3: CacheThru_write (in /usr/local/bin/lynx)
==6922==  Address 0x1BBF5512 is 26 bytes inside a block of size 300 
alloc'd
==6922==    at 0x1B906EDD: malloc (vg_replace_malloc.c:131)
==6922==    by 0x8115729: HTSACopy (in /usr/local/bin/lynx)
==6922==    by 0x80B2562: HTML_start_element (in /usr/local/bin/lynx)
==6922==    by 0x81101CE: start_element (in /usr/local/bin/lynx)
==6922==    by 0x810D9D6: SGML_character (in /usr/local/bin/lynx)
==6922==    by 0x8102E83: SGML_write (in /usr/local/bin/lynx)
==6922==    by 0x80C58F3: CacheThru_write (in /usr/local/bin/lynx)
==6922==    by 0x811AA2E: HTGzFileCopy (in /usr/local/bin/lynx)
==6922==    by 0x8119BE6: HTParseGzFile (in /usr/local/bin/lynx)
==6922==    by 0x80F7171: decompressAndParse (in /usr/local/bin/lynx)

I'll work on lynx in the morning (this fix is simple, but the other one
will probably take a few hours).

I spent a few hours testing with valgrind this week, but for whatever
reason overlooked this bug.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net