At 12:32 23/11/01 -0600, Gilles Detillieux wrote:
>According to Marcus Valentine:
>> At 11:04 23/11/01 -0600, Gilles Detillieux wrote:
>> >According to Marcus Valentine:
>> >> On my intranet, there is a unfortunate xls file. Although the xls
file is
>> >> only 266 kb big, converting it with xlhtml 0.3 at the command line
results
>> >> in a 37 Mb html file. (Running with the -a option [aggressive html
>> >> optimization] reduces the file size to 23 Mb).
>> >> 
>> >> Running htdog 3.1.5 with doc2html.pl version 3 calling xlhtml 0.3
results
>> >> in an htdig core dump when it gets to this document. Htdig runs on Linux
>> >> Redhat 6.2
>> >...
>> >> Read a total of 272384 bytes
>> >> Aborted (core dumped)
>> >
>> >I find it interesting that the reason for the core dump is an abort, and
>> >not a segfault or something like that.  Aborts are usually a deliberate
>> >action by the program, and are usually preceded by an explanation.  The
>> >only aborts in 3.1.5 are in the DB code, I think.  A stack backtrace might
>> >provide some clues as to the problem and hopefully a solution or
prevention.
>> 
>> I don't know how to do this at the moment. Could you not reproduce the
>> problem by creating an enormous html file (some real stuff at the beginning
>> and then tens of thousands of lines with <td>&nbsp;</td>) and letting htdig
>> loose on it?
>
>This assumes that the problem leading htdig to abort is the enormity of
>the html file it gets from doc2html.pl, or the large number of repeated
>td's with &nbsp;.  This is by no means a given.  There are very likely
>other factors involved, and trying to reproduce the problem with the
>little information I have would most likely be a wild goose chase.
>
>All you need to do is run "gdb /path/to/htdig /path/to/core" and do a
>"bt" command, as explained in the FAQ.

Here's another back trace. This one was generated when htdig encounter a
file that began:

-0.348096
-0.070797
0.204147
0.393852
0.449417

and then continued in a similar vein for 921595 lines (file size was 8.3M).
This time no external convertors were involved. There seems to be a problem
when htdig encounters big files. I've got max_doc_size set big (20 000 000)
as I've got some sizable pdfs on my system. I will exclude the files just
containing numbers (I missed them previously), but I still have the
previous problem with xlhtml.

Thanks

Marcus Valentine

* * * *

$ gdb /usr/sbin/htdig ./core
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...(no debugging symbols
found)...
Core was generated by `/usr/sbin/htdig -i -s -v -c htdigintranet.conf 2'.
Program terminated with signal 6, Aborted.
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Reading symbols from /usr/lib/libstdc++-libc6.1-1.so.2...done.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
Reading symbols from /lib/libnss_files.so.2...done.
Reading symbols from /lib/libnss_nisplus.so.2...done.
Reading symbols from /lib/libnsl.so.1...done.
Reading symbols from /lib/libnss_nis.so.2...done.
Reading symbols from /lib/libnss_dns.so.2...done.
Reading symbols from /lib/libresolv.so.2...done.
#0  0x400a6d21 in __kill () from /lib/libc.so.6
(gdb) bt
#0  0x400a6d21 in __kill () from /lib/libc.so.6
#1  0x400a6996 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2  0x400a80b8 in abort () at ../sysdeps/generic/abort.c:88
#3  0x40057e55 in __default_terminate () from
/usr/lib/libstdc++-libc6.1-1.so.2
#4  0x40058c1a in terminate () from /usr/lib/libstdc++-libc6.1-1.so.2
#5  0x40058cf8 in __eh_alloc (size=36) from /usr/lib/libstdc++-libc6.1-1.so.2
#6  0x40058d88 in __cp_push_exception (value=0xc1d9fd0, type=0x4006af84,
    cleanup=0x4005b604 <bad_alloc::~bad_alloc(void)>) from
/usr/lib/libstdc++-libc6.1-1.so.2
#7  0x4005a252 in __builtin_new (sz=40) from /usr/lib/libstdc++-libc6.1-1.so.2
#8  0x805a86b in strcpy () at ../sysdeps/generic/strcpy.c:30
#9  0x80521db in strcpy () at ../sysdeps/generic/strcpy.c:30
#10 0x804f531 in strcpy () at ../sysdeps/generic/strcpy.c:30
#11 0x8050d25 in strcpy () at ../sysdeps/generic/strcpy.c:30
#12 0x805099a in strcpy () at ../sysdeps/generic/strcpy.c:30
#13 0x805036d in strcpy () at ../sysdeps/generic/strcpy.c:30
#14 0x8054b60 in strcpy () at ../sysdeps/generic/strcpy.c:30
#15 0x400a09cb in __libc_start_main (main=0x80543f0 <strcpy+40380>, argc=7,
argv=0xbffffb64,
    init=0x8049da4 <_init>, fini=0x8090eac <_fini>, rtld_fini=0x4000aea0
<_dl_fini>, stack_end=0xbffffb5c)
    at ../sysdeps/generic/libc-start.c:92
(gdb)

* * * *

_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to