[squid-dev] [PATCH] shared_memory_locking

[Alex Rousskov]

On 03/10/2016 08:32 PM, Eliezer Croitoru wrote:

> Can this be verified in any way?

Verify that I am not imagining things? Sure! If looking at fatal()
itself is not enough to realize that it does not log the FATAL message
until _after_ calling a few "heavy" functions (which may fail on their
own), then just call "abort()" from releaseServerSockets() to emulate
such a failure, and you will not see any FATAL messages from Squid, no
mater how many times it calls fatal() or fatalf().

Alex.



> On 11/03/2016 05:28, Amos Jeffries wrote:
>> If there is a bug in fatalf() that's something else that needs to be
>> fixed. But there has been no sign that I'm aware of about any such issue
>> in for any of the hundreds of other calls to it. Please dont make bad
>> code here just for that.