) quit
Do you need all the other stuff right from the start ?
kind regards,
Jan
-Ursprüngliche Nachricht-
Von: Amos Jeffries [mailto:squ...@treenet.co.nz]
Gesendet: Dienstag, 21. Juli 2009 11:57
An: Zeller, Jan
Cc: squid-users@squid-cache.org
Betreff: Re: AW: AW: AW: [squid-users] Squid
Betreff: Re: AW: AW: AW: [squid-users] Squid 3.1.0.11 beta is available
Zeller, Jan wrote:
Hi Amos,
I entered this :
# gdb --args ./squid -NCXd9
and got this :
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org
]
Gesendet: Dienstag, 21. Juli 2009 12:22
An: Zeller, Jan
Cc: squid-users@squid-cache.org
Betreff: Re: AW: AW: AW: AW: [squid-users] Squid 3.1.0.11 beta is available
Zeller, Jan wrote:
No problem Amos I consulted the man gdb ;) and I also tried run in the gdb
console but there is still
-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...
#
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
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 Koolmarcus.k...@urlfilterdb.com wrote:
my 2 cents:
someone
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