Just break on SIGABRT and SIGSEGV. The actual place in the code where
things failed will be slightly further up the callstack than the break
point but it -will- be triggered.
Just remember to ignore SIGPIPE's or you'll have a strangely failing Squid. :)
adrian
2009/7/21 Marcus Kool :
> my 2 ce
Er.. not really
The failing line gets invoked very often, so setting a breakpoint
there would be quite time-consuming.
I really hope that there is some other way.
(crossing fingers)
Francesco
On Tue, Jul 21, 2009 at 4:49 PM, Marcus Kool wrote:
> my 2 cents:
> someone needs to explain how to set
my 2 cents:
someone needs to explain how to set a breakpoint
because when the assertion fails, the program exits
(see previous emails: Program exited with code 01)
The question is where to set the breakpoint
but probably Amos knows where to set it.
Marcus
Silamael wrote:
-BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zeller, Jan wrote:
> Hi Amos,
>
> I now explicitly enabled
>
> --enable-stacktraces Enable automatic call backtrace on fatal errors
>
> during the build and added CFLAGS="-g -ggdb" in front of ./configure
> but the result seems to be the same...
>
Hi Amos,
I now explicitly enabled
--enable-stacktraces Enable automatic call backtrace on fatal errors
during the build and added CFLAGS="-g -ggdb" in front of ./configure
but the result seems to be the same...
# ./squid -v
Squid Cache: Version 3.1.0.11
configure options: '--prefix=/opt/squi
