[
https://issues.apache.org/jira/browse/MESOS-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838849#comment-15838849
]
Andrew Schwartzmeyer commented on MESOS-6815:
---------------------------------------------
Work in progress is here: https://github.com/andschwa/glog/tree/test, with an
open but unfinished pull request here: https://github.com/google/glog/pull/151.
This is currently paused. The status is that stack tracing works, but relying
on a signal handler to report the stack trace does not provide the desired
behavior. On Linux, the stack trace is reported from the thread that the signal
was called; but it seems on Windows that the stack trace is reported from the
thread on which the signal handler was installed, regardless of the thread from
which it was called. I believe the correct approach is to slightly change how
Glog reports stack tracing (at least for Windows) to not rely on signal
handlers.
> Enable glog stack traces when we call things like `ABORT` on Windows
> --------------------------------------------------------------------
>
> Key: MESOS-6815
> URL: https://issues.apache.org/jira/browse/MESOS-6815
> Project: Mesos
> Issue Type: Bug
> Components: stout
> Reporter: Alex Clemmer
> Assignee: Andrew Schwartzmeyer
> Priority: Critical
> Labels: microsoft, windows-mvp
>
> Currently in the Windows builds, if we call `ABORT` (etc.) we will simply
> bail out, with no stack traces.
> This is highly undesirable. Stack traces are important for operating clusters
> in production. We should work to enable this behavior, including possibly
> working with glog to add this support if they currently they do not natively
> support it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
