Hello, I got another error with this webpage (http://islammemo.cc/akhbar/aame/page/4595), again elinks crashes if I open the page in virtual terminal (TERM=linux), yet does not crash if I open the page in gnome terminal (TERM=xterm).
Here's the error I got: x843e3b0:52 overflow detected free() @ /tmp/buildd/elinks-0.13~20080907/src/document/html/tables.c:902, alloc'd at /tmp/buildd/elinks-0.13~20080907/src/document/html/renderer.c:2232 Forcing core dump! Man the Lifeboats! Women and children first! But please DO NOT report this as a segfault!!! It is an internal error, not a normal segfault, there is a huge difference in these for us the developers. Also, noting the EXACT error you got above is crucial for hunting the problem down. Thanks, and please get in touch with us. ELinks crashed. That shouldn't happen. Please report this incident to the developers. If you would like to help to debug the problem you just uncovered, please keep the core you just got and send the developers the output of 'bt' command entered inside of gdb (which you run as: gdb elinks core). Thanks a lot for your cooperation! ELinks 0.13.GIT Built on Sep 7 2008 07:31:24 Features: Debug, IPv6, gzip, bzip2, UTF-8, Combining characters, Periodic Saving, Viewer (Search History, Timer, Marks), Cascading Style Sheets, Protocol (Authentication, BitTorrent, File, CGI, Finger, FSP, FTP, Gopher, HTTP, NNTP, SMB, URI rewrite, User protocols), SSL (GnuTLS), MIME (Option system, Mailcap, Mimetypes files), LED indicators, Bookmarks, Cookies, ECMAScript (SpiderMonkey), Form History, Global History, Scripting (Lua, Guile, Perl, Python, Ruby, Spidermonkey ECMAScript), Exmode, Goto URL History elinks(dump_backtrace+0x1c)[0x81326ac] elinks[0x80e2d0d] elinks[0x80e2c14] [0xb7f24420] elinks(force_dump+0x69)[0x8132af9] elinks(debug_mem_free+0x7c)[0x8135f1c] elinks[0x80a9e34] elinks(format_table+0x18d7)[0x80ac857] elinks(html_table+0x9b)[0x80b0b2b] elinks(parse_html+0xdde)[0x80b52de] elinks(format_html_part+0x2c5)[0x80a4f25] elinks(render_html_document+0x1af)[0x80a549f] elinks(render_document+0x7ee)[0x8097e9e] elinks(render_document_frames+0x221)[0x8098281] elinks(draw_formatted+0x5c)[0x813e56c] elinks(doc_loading_callback+0x18f)[0x812256f] elinks[0x80da217] elinks[0x80db864] elinks(add_keepalive_connection+0x1e8)[0x80dbf48] elinks[0x81071fe] On Tue, Sep 09, 2008 at 01:10:49AM +0300, Kalle Olavi Niemitalo wrote: > أحمد المحمودي <[EMAIL PROTECTED]> writes: > > > Unfortunately I cannot find any *core* files after elinks crashes ! > > You may be able to change that with ulimit -c in bash. > However, for easily reproduceable crashes, I find it easier > to run elinks within gdb, because that way there is no core > file that I'd have to delete later. ---end quoted text--- -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer SySDSoft, Inc. GPG KeyID: 0x9DCA0B27 (@ subkeys.pgp.net) GPG Fingerprint: 087D 3767 8CAC 65B1 8F6C 156E D325 C3C8 9DCA 0B27 _______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
