Comment 8 for bug 1426095
Revision history for this message
| Alex Rousskov (rousskov) wrote Re: eClamav cannot initialize and crashes Squid repeatedly | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
You might be battling several problems here. One of them is probably related to the fact that Squid asserts while handling an earlier segfault -- you get a [useless] stack trace from the assertion instead of the stack trace from the earlier segfault. I can suggest two possible (untested in your environment) solutions, in the order of preference:
1. Start Squid from gdb itself.
2. Start Squid with command-line options -N and -C.