> On Thu, Jul 05, 2007, Amos Jeffries wrote: >> >> I have been overlooking these for a while on the assumption that it was >> gdb catching something when it should have left it. I have just started >> wondering if this was in fact bad unexpected behaviour for the squid >> signals. Should I be looking into it? > > Nope! > > put this in ~/.gdbinit: > > handle all nostop noprint > handle SIGSEGV stop > handle SIGPIPE stop >
Oh great. Thanks Adrian. Amos
