[squid-users] Survey on assertions: When the impossible happens

[Marcus Kool]

>> This is not really #4. It is an enhancement for any of the three
>> options. IIRC, Squid even supported gdb stack tracing natively on some
>> platforms (but a script would arguably be better, except for busy
>> proxies that cannot be blocked for 2-4 seconds it takes to run that script).
>>
>
>
> This already exists. Squid does it *right now*.
>
> You never received a "The Squid Cache (version %s) died." email ?

Nope.

> When mail [1] is working on the proxy Squid will use it to send an email
> to the configured administrator email address [2], root@ address for the
> proxies private hostname [3], or root@ address for the proxies public
> hostname [4] - in that order or preference.
>   - Of course, far too many people dont use FQDN for those config settings...
>
>
> [1] http://www.squid-cache.org/Doc/config/mail_program/
> [2] http://www.squid-cache.org/Doc/config/mail_from/
> [3] http://www.squid-cache.org/Doc/config/unique_hostname/
> [4] http://www.squid-cache.org/Doc/config/visible_hostname/

I learned something today :-)  (does not happen every day)

>>> The stack dumps will be save in an assertion failure log file which admins
>>> can send to Squid developers.
>>>
>
>
> If Squid is also built with --enable-stacktraces a stack trace will be
> recorded in cache.log after FATAL messages.
> - Of course. Speed at any cost "needs" prohibit doing anything that
> might slow down the Squid restart process. So that gets disabled.

Hmm. are you suggesting that this wonderful feature is not widely used?

If not, then calling gdb is preferred.
gdb also prints parameters, local variables and contents of data structures etc.
hence superior than backtrace().

Marcus

>
> Amos