-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
Currently, the glog test suite (not the glog library itself) relies on precise
values of few errno constants (ENOENT=2, EINTR=4, ENXIO=6, ENOEXEC=8).
This is not POSIX compliant[1], as actual err…
-
```
What steps will reproduce the problem?
1. call InstallFailureSignalHandler()
2. kill the process with SIGTERM(15)
3. glog print callstack, and then quit.
What is the expected output? What do you …