"Lightfoot.Michael" wrote: > As I stated (not very clearly) I have had no success in getting a core > dump from squid 2.5. I have (before Robert's suggestion and since to > make sure I hadn't missed anything) read the FAQ section on core dumps > and debugging. I am considering running in debug mode for a while, but > this _is_ a produciton server and I don't want to impact any further on > my users.
Well, without a stack trace there is very little that can be done, by either SmartFilter or the Squid developers, unless you get as far as reaching a SmartFilter developer who manages to reproduce the fault on his machine. > There are at least 2 other readers of this list (I am in communication > with 2) who are getting _precisely_ the same errors (either a seg > violation or the particular assert failure in store_client.c.) We > _know_ it is Secure Computing's problem. We are trying to get enough > info to force them to fix the damn problem, but it is a little difficult > when we aren't familiar enough with the squid source to work out what is > happening and we are commiunicating via email with a moving target of > help desk people who often don't appear to talk to each other. :-( If you manage to get a stack trace of when it happens you will have a lot higher chances I think. Regards Henrik
