You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When glog is built with Bazel, failure signal handler is unable to print stack trace.
*** Aborted at 1531880485 (unix time) try "date -d @1531880485" if you are using GNU date ***
PC: @ 0x0 (unknown)
zsh: segmentation fault bazel run :hello
On Linux, no stacktrace is shown. On macOS, it enters deadlock for some reason and can be killed only with SIGKILL (no Ctrl+C), which is worse.
The text was updated successfully, but these errors were encountered:
nya3jp
added a commit
to nya3jp/glog
that referenced
this issue
Jul 18, 2018
We need at least following defs to be set to print stacktrace in
failure signal handler.
- HAVE_UNWIND_H: On Linux and macOS. unwind.h is usually present
by default on those systems.
- HAVE_DLADDR: On macOS.
Windows is not cared because glog can not be built with bazel
on Windows today.
Resolvesgoogle#346.
nya3jp
added a commit
to nya3jp/glog
that referenced
this issue
Jul 18, 2018
We need at least following defs to be set to print stacktrace in
failure signal handler.
- HAVE_UNWIND_H: On Linux and macOS. unwind.h is usually present
by default on those systems.
- HAVE_DLADDR: On macOS.
Note that today glog does not build with Bazel on Windows.
Resolvesgoogle#346.
When glog is built with Bazel, failure signal handler is unable to print stack trace.
*** Aborted at 1531880485 (unix time) try "date -d @1531880485" if you are using GNU date ***
PC: @ 0x0 (unknown)
zsh: segmentation fault bazel run :hello
On Linux, no stacktrace is shown. On macOS, it enters deadlock for some reason and can be killed only with SIGKILL (no Ctrl+C), which is worse.
The text was updated successfully, but these errors were encountered: