أحمد المحمودي <[EMAIL PROTECTED]> writes: > When I attempt to open a certain HTML file, elinks core dumps giving > out the following error:
Unfortunately I cannot reproduce this crash with your attachment. I ran ELinks like this: $ LD_LIBRARY_PATH=/home/Kalle/prefix/i686-pc-linux-gnu/lib ~Kalle/build/i686-pc-linux-gnu/elinks-0.13_O2_small/src/elinks -no-home -no-connect ~Kalle/trans/article_17686.shtml ELinks displayed the page, although I guess not correctly because it does not support right-to-left text. Then I pressed q and Enter to quit. There was no crash. I also tried a few other configurations. These tests were all with commit 7de8b9940c96f51c55c2706ed9aa6ad11257d7ee which I think what was in last night's elinks-0.13 snapshot. Please try doing the same with your elinks binary. Do you get the crash that way or do you have to do something else (e.g. follow some links, enable Javascript, or load the HTML via HTTP rather than from a file) to trigger the crash? Please also list the options you gave to the configure script, the version of your compiler, and the type and size (e.g. 80x25) of your terminal. > elinks(dump_backtrace+0x1c)[0x81324ec] > elinks[0x80e2b4d] > elinks[0x80e2a54] > [0xb7fc3420] > elinks(force_dump+0x69)[0x8132939] > elinks(debug_mem_free+0x50)[0x8135d30] > elinks(done_document+0x1af)[0x809488f] Unfortunately the backtrace displayed by ELinks is not as good as what gdb can provide. Please try to get line numbers in the backtrace by reproducing the crash under gdb or by running gdb on a core file. It would be especially interesting to know the line number within done_document. And if you can reproduce the crash under valgrind, the output From that will probably show both where the memory was originally freed and where it's being freed the second time. That would be very useful.
pgpWs4vMJLUgu.pgp
Description: PGP signature
_______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
