[SQU] bug in 2.4-tarball or ntlm.patch?

Hi,

I've taken the daily snapshot of 2.4 (tarball from www.squid-cache.org) and
applied ntlm.patch (over http from squid.sourceforge.net).

After "tar -xzvf; patch; autoconf; autoheader; su - squid; configure; make
all; make install" (without any errors), I tried to initialize the cache
with "squid -z" and process is killed with the following error message:
"Segmentation Fault" (no cache-dirs are created!)! No difference by using
only "squid"!

I tried this several times during the last 5 days ( 5 different tarballs!),
on SuSE-Linux 6.3 and SuSE-Linux 7.0, on original kernels 2.2.13, 2.2.16, on
compiled kernels 2.2.13, 2.2.16, on 4 different i586/i686-machines, with
installed kernel-includes and with many combinations of different
configure-options, and each time the same result.

I have no problems, if I install squid-2.3stable4 (with 6 patches) or
squid-2.4.devel4 (with 6 patches) on the same machines!
Also I have enough free memory (about 100 MBs).

Five weeks ago, I used the tarball and the ntlm.patch on the same machines
without any problems.

Can anybody tell me if I'm doing something wrong or is there a bug in the
tarball?

----------------------------------------------------------
Udo Busch - NT-Projektgruppe -
Bezirksfinanzdirektion München Abt. VII
Mailingerstr. 11, 80636 München
Tel.: (089)2190 - 1453; Fax: -1200
E-Mail: udo.busch@bfd-m.bayern.de
--------------------------------------------------------------------------

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html