You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by acaciocenteno <gi...@git.apache.org> on 2014/09/09 16:30:51 UTC
[GitHub] trafficserver pull request: proxy.config.stack_dump_enabled
GitHub user acaciocenteno opened a pull request:
https://github.com/apache/trafficserver/pull/109
proxy.config.stack_dump_enabled
While debugging the issues we've had with ATS, we needed to generate core files, but by default ATS handles the SIGSEGV signal and prints the backtrace to traffic.out. We've find out, though, that there's a config setting that disables this behavior, allowing core files to be generated, and decided we should add this information to the doc as others, specially newcomers to ATS, may find it useful.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aziontech/trafficserver corefile
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/109.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #109
----
commit 227e6a45b7a1d50979f70007c018b686d534ff0f
Author: Acácio Centeno <ac...@gmail.com>
Date: 2014-09-08T14:31:56Z
proxy.config.stack_dump_enabled
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] trafficserver pull request: proxy.config.stack_dump_enabled
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/109
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---