On Fri, 23 Jan 2004, Andres Kroonmaa wrote: > This would leave more precise and verbose trace of last N^2 debug statements > that have been passed. After you identify the function that crashes, you > can take approach I suggested initially to catch the crash with gdb and > have full backtrace just before stack gets smashed.
Equally interesting. One of them obviously suffices. Both approaches give slightly better information than a stack trace wrt the total code flow due to Squid design. The ring buffer approach the most accurate. Regards Henrik
