Re: Debugging ATS crashers with gdb

2011-06-08 Thread Leif Hedstrom
I captured some of this from the discussions in https://cwiki.apache.org/confluence/display/TS/Filing+useful+bug+reports Please add / edit this as appropriate. -- leif

Re: Debugging ATS crashers with gdb

2011-06-08 Thread Leif Hedstrom
On 06/04/2011 02:28 PM, Leif Hedstrom wrote: 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 . One more tip for debugging with gdb, this one is suggested from John: (gdb) handle SIGPIPE nopass nos

Re: Debugging ATS crashers with gdb

2011-06-04 Thread Leif Hedstrom
On 06/04/2011 02:28 PM, Leif Hedstrom wrote: 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 . One more thing: You might have to set this in records.config as well: CONFIG proxy.config.core_limi

Re: Debugging ATS crashers with gdb

2011-06-04 Thread Igor Galić
- 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

Re: Debugging ATS crashers with gdb

2011-06-04 Thread Leif Hedstrom
On 06/04/2011 05:07 PM, Igor Galić wrote: This is *bad* it will be inherited down to *all* processes started by root, which are bound to be many. traffic_server runs as nobody (per default) so add that user too: Sure, valid point. If you are concerned about this, use the first option of doing

Re: Debugging ATS crashers with gdb

2011-06-04 Thread Igor Galić
- 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 t