Michael Rogers wrote:
> Matthew Lye wrote:
> > I'm noticing an extraordinary number of outgoing attempts to connect
> > to Foxy 1.9.9.0 clients in Taiwan and Hong Kong as GTKG starts up,
> > here. Could the [swarms of] Foxy clients which are [always] failing
> > to connect as incoming connec
Matthew Lye wrote:
> I'm noticing an extraordinary number of outgoing attempts to connect
> to Foxy 1.9.9.0 clients in Taiwan and Hong Kong as GTKG starts up,
> here. Could the [swarms of] Foxy clients which are [always] failing
> to connect as incoming connections nonetheless be ending up i
I'm noticing an extraordinary number of outgoing attempts to connect
to Foxy 1.9.9.0 clients in Taiwan and Hong Kong as GTKG starts up,
here. Could the [swarms of] Foxy clients which are [always] failing
to connect as incoming connections nonetheless be ending up in the
GTKG hostcache?
-
Matthew Lye wrote:
> The unfinished(?) implementation of TRACK_MALLOC control in "lib/
> halloc.h" is currently causing several halloc functions to remain
> undefined if TRACK_MALLOC is not defined.
There I fixed it.
--
Christian
--
The unfinished(?) implementation of TRACK_MALLOC control in "lib/
halloc.h" is currently causing several halloc functions to remain
undefined if TRACK_MALLOC is not defined.
(Specifically, halloc, hfree, hrealloc, halloc0, and hcopy, as called
by matching.c, settings.c, share.c, and tls_commo
