squid exiting on signal 6

Hello,

Our primary proxy server, running FreeBSD 3.1 and squid-2.1.PATCH2
is having problems. We are seeing messages like the following:
pid 76345 (dnsserver), uid 65534: exited on signal 10 (core dumped)
pid 77393 (squid), uid 65534: exited on signal 6

A traceback on the dnsserver core shows:
#0 0x200cc96c in __ns_name_unpack ()
#1 0x200ccb7d in __ns_name_uncompress ()
#2 0x200cc24e in __dn_expand ()
#3 0x200c107c in _gethostbyhtaddr ()
#4 0x200c19ca in _gethostbydnsaddr ()
#5 0x200c04ae in gethostbyaddr ()
#6 0x8048881 in exit ()
#7 0x8048b1a in exit ()
#8 0x8048755 in exit ()

We aren't getting a core for the signal 6 on squid itself.
We added several 'ulimit' options to RunCache to increass the maximum
datasize, stacksize, and memoryuse. Our process is typically no more
than 140M, and our ulimit is 512MB!
Does anyone have suggestions for debugging this problem? Will running
as root instead of nobody allow us to capture a core dump? According
to the FreeBSD manpages, SIGABRT should dump core, so I am assuming it
doesn't because the process is changing it's uid.

Please copy me via email also, thanks.

-Andrew

-- 
-----------------------------------------------------------------
Andrew Gillham                            | This space left blank
gillham@whirlpool.com                     | inadvertently.
I speak for myself, not for my employer.  | Contact the publisher.