On 18/02/2016 4:54 a.m., William Lima wrote: > Hi Alex! > > Why not? I had the same problem. It is the same assert - but being hit from very different causes. Fixing one cause does not fix all the other cause(s). One has to look further down the debugger stack traces to see where the brokn code actually is. We have a number of these ways to hit String assert() being found and no doubt more will continue to be found until we get rid of the broken String class entirely from Squid. Which is why patches like yours are so important to get rid of the String variables entirely ASAP rather than just fixing how it gets used in that one code path. Thank you for that. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
