أحمد المحمودي writes:
> I confirm that I got the same problem with elinks 0.13 (20081129
> snapshot).
ELinks 0.10.6, 0.11.0, 0.11.5, 0.12pre1, and 0.12pre2 all crash.
The trigger is that there is no newline after the final .
Small test case:
Double-free crash in USEMAP
http://elinks.cz/"; al
Here's what elinks printed on screen when crashing:
0x8e1ff20:320 double free free() @
/tmp/buildd/elinks-0.13~20081129/src/document/html/parser.c:797, alloc'd at
/tmp/buildd/elinks-0.13~20081129/src/document/html/parser.c:747
0x8e1ff20:320 bad alloc_header block free() @
/tmp/buildd/elinks-0.1
On Mon, Dec 29, 2008 at 12:52:58PM +0100, Paul B. Mahol wrote:
> Here is link:
>
> http://www.afn.org/~afn04133/doom1.htm
>
> Selecting last USEMAP will kill elinks due to what appears to be
> memory allocation problem.
---end quoted text---
I confirm that I got the same problem with elinks 0.13
Here is link:
http://www.afn.org/~afn04133/doom1.htm
Selecting last USEMAP will kill elinks due to what appears to be
memory allocation problem.
--
Paul
___
elinks-dev mailing list
elinks-dev@linuxfromscratch.org
http://linuxfromscratch.org/mailman/li
