trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Galić <i.ga...@brainsware.org>
Subject Re: Debugging ATS crashers with gdb
Date Sat, 04 Jun 2011 23:20:31 GMT


----- Original Message -----
> 
> 
> ----- Original Message -----
> > Hi all,
> >
> > these questions pops up all the time, how to get a stack traces
> > etc.
> > from a crashing ATS installation. So, here are some quick tips .
> >
> > First, it's important to have a properly built ATS version for
> > debugging to be efficient. The "best" option is to build ATS with
> > something like this:
> >
> > #! /bin/sh
> > #
> > # Created by configure
> >
> > "./configure" \
> > "--enable-static-libts" \
> > "--enable-debug" \
> > "$@" Next, Linux can be finicky when it comes to generating core
> > files, so I'd recommend the following sysctl configs:
> >
> > kernel.core_uses_pid = 1
> > kernel.core_pattern = /tmp/core This tells the kernel to dump the
> > core file into /tmp, with a name like core.12345. Also, you might
> 
> For more info see core(5)
> http://www.freebsd.org/cgi/man.cgi?core
> http://www.kernel.org/doc/man-pages/online/pages/man5/core.5.html


You should really just ignore everything I said in my last email
past this point. It was terribly misinformed.

i

-- 
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/

Mime
View raw message