[
https://issues.apache.org/jira/browse/TS-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283904#comment-15283904
]
ASF subversion and git services commented on TS-4441:
-----------------------------------------------------
Commit ace9caae532f5accd51cfb864c0b43bf5f6a470b in trafficserver's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ace9caa ]
TS-4441: Stop dumping core on fatal errors.
On a fatal error, the core file is rarely useful, and there is a
real risk of filling up a disk with cores when we get a bad
configuration. Rather than dumping core when logging a fatal error,
just exit.
Add a new API ink_abort() that logs a fatal error followed by
abort(3) rather than exit(3). Use this in ink_assert() and other
places where it makes sense to dump core.
> Fatal() should not dump core
> ----------------------------
>
> Key: TS-4441
> URL: https://issues.apache.org/jira/browse/TS-4441
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, Logging
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 7.0.0
>
>
> Diagnostics of level {{Fatal}} or higher cause Traffic Server to dump core.
> This makes it unfriendly to use since a we could end up leaving a lot of core
> files, which are not likely to be useful.
> {{ink_fatal_va}} should just exit without dumping core.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
