Apparently on Solaris 10 a SA_SIGINFO signal handler can be invoked with
a nil info argument. I would not have believed it but I've now seen it
happen, and the sigaction man page actually says "If the second argument
is not equal to NULL, it points to a siginfo_t structure...." So, if
that happens, don't crash.
Also fix another case where we want to make sure that &T{} does not
allocate.
Reviewed-on: https://go-review.googlesource.com/33150
From-SVN: r242403
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| config | Loading commit data... | |
| go | Loading commit data... | |
| runtime | Loading commit data... | |
| testsuite | Loading commit data... | |
| LICENSE | Loading commit data... | |
| MERGE | Loading commit data... | |
| Makefile.am | Loading commit data... | |
| Makefile.in | Loading commit data... | |
| PATENTS | Loading commit data... | |
| README | Loading commit data... | |
| README.gcc | Loading commit data... | |
| VERSION | Loading commit data... | |
| aclocal.m4 | Loading commit data... | |
| config.h.in | Loading commit data... | |
| configure | Loading commit data... | |
| configure.ac | Loading commit data... | |
| godeps.sh | Loading commit data... | |
| match.sh | Loading commit data... | |
| merge.sh | Loading commit data... | |
| mkrsysinfo.sh | Loading commit data... | |
| mksigtab.sh | Loading commit data... | |
| mksysinfo.sh | Loading commit data... | |
| mvifdiff.sh | Loading commit data... | |
| sysinfo.c | Loading commit data... |