Summary: | www/squid: Segmentation fault | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Sergey Anokhin <admin> |
Component: | Individual Port(s) | Assignee: | Eugene Grosbein <eugen> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Only Me | CC: | emz, eugen, timp87 |
Priority: | --- | Keywords: | crash, needs-qa |
Version: | Latest | Flags: | eugen:
maintainer-feedback+
|
Hardware: | Any | ||
OS: | Any |
Description
Sergey Anokhin
2019-05-16 12:41:07 UTC
Same stuff here (almost) on 12.0-R with slightly different port flags. What is more surprising, only one of the two almost identical servers is affected. On the affected machine squid crashes right after start. But here's the thing: in my case the basic_pam_auth helper crashes, not the main process. Any help is appreciated here! (In reply to timp87 from comment #2) I've made some researchements, so, it seems that we had two bugs: 1. Unknown cause of core dumped 2. Core dumped with blank variable unique_hostname and -X parameter. The combination of these two factors gives core dumped (tested on latest port version squid-4.8_1) I suspect that the bug was dissapear after upgading to squid 4.8 (In reply to Sergey Anokhin from comment #3) Is that to say the crash is no longer reproducible with squid 4.8? In off-track conversation submitter confirmed that version 4.8 runs without crash unless debugging switch -X is added manually that is not the case for our port. |