At 11:56 PM -0700 3/1/00, Tim Rightnour wrote:
>The data in #6 looks extremely hosed.. This is not the problem I was seeing
>earlier.. once again.. I've left it in gdb for you.
Yes, this time it's somehow a segfault!? The data in #6 is actually
correct, this is what your URL:
<http://mail-index.netbsd.org/tech-net/1998/01/29/0000.html> looks
like after it's gone through url_part_aliases and common_url_parts.
If you count out the full 48 chars reserved by the len field, you see
that the stuff at the end of the string is just that--junk beyond the
length.
It looks like somehow it's hitting a memory wall--it tried to
allocate some memory for this and it couldn't. How early did this
happen in a run? Is this now a consistent thing? Is there any chance
that you've run out of RAM?
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
>Breakpoint 1 at 0x2384f: file DB2_db.cc, line 393.
>(gdb) run
>Starting program: /u2/util/nbsdwww/htdig/bin/htdig
>
>Program received signal SIGSEGV, Segmentation fault.
>0x4015e068 in _GLOBAL_OFFSET_TABLE_ ()
>(gdb) bt
>#0 0x4015e068 in _GLOBAL_OFFSET_TABLE_ ()
>#1 0x4015001f in __errno ()
>#2 0x4014dd8a in malloc ()
>#3 0x6042f in __builtin_new ()
>#4 0x60095 in __builtin_vec_new ()
>#5 0x26de2 in String::allocate_fix_space (this=0xbfbfd32c, len=48)
> at String.cc:587
>#6 0x26e55 in String::copy (this=0xbfbfd32c,
> s=0x802a100
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
