1.1.22 Segmentation Violation is in BIN_TREE

Turns out that switching to a SPLAY_TREE option corrects the problem -
the segmentation violation comes when the binary tree is attempting to
search out an IP address for the ACL functionality:

Upon inserting debug lines into the lib/tree.c and acl.c code, I
determined that the segmentation fault is occurring as follows:

1998/06/29 15:00:03| aclCheck: checking 'http_access allow comshare'
1998/06/29 15:00:03| aclMatchAclList: checking comshare
1998/06/29 15:00:03| aclMatchAcl: checking 'acl comshare src 130.211.0.0/255.255.0.0'
1998/06/29 15:00:03| aclMatchIp[bin]: searching for '130.211.100.200'
tree_srch: t = 3158352
tree_srch: i_comp = -1
tree_srch: t = 915584
tree_srch: i_comp = 1
tree_srch: &t->right = 915592
tree_srch: t = 0
tree_srch() returns NULL
1998/06/29 15:00:03| aclMatchIp: '130.211.100.200' NOT found
1998/06/29 15:00:03| aclMatchAclList: returning 0
1998/06/29 15:00:03| aclCheck: checking 'http_access allow localhost'
1998/06/29 15:00:03| aclMatchAclList: checking localhost
1998/06/29 15:00:03| aclMatchAcl: checking 'acl localhost src 127.0.0.1/255.255.255.255'
1998/06/29 15:00:03| aclMatchIp[bin]: searching for '130.211.100.200'
tree_srch: t = 3158328
tree_srch: i_comp = -1
tree_srch: t = 134217774
Abort trap
FATAL: Received Segment Violation...dying.
1998/06/29 15:00:03| storeWriteCleanLog: Starting...

For some reason, it's now crashing on the 127.0.0.1/32 acl, whereas
earlier in my testing process it crashed on that first ACL lookup.

As I'm not too familiar with the binary tree functionality of Squid,
I'll leave chasing this down to its final resolution to some other
intrepid Squid hacker... Please let me know if you'd like other
debugging information or test runs.

        -Mike Pelletier.

--
 "[It will] be very hard to increase browser share on the merits of
  [Internet Explorer] alone.  It will be more important to leverage
  the OS asset to make people use IE instead of Navigator."
			-- Christian Wildfeuer, a Microsoft Manager