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 |
|---|---|---|
| .. | ||
| gofrontend | Loading commit data... | |
| ChangeLog | Loading commit data... | |
| Make-lang.in | Loading commit data... | |
| README.gcc | Loading commit data... | |
| config-lang.in | Loading commit data... | |
| gccgo.texi | Loading commit data... | |
| go-backend.c | Loading commit data... | |
| go-c.h | Loading commit data... | |
| go-gcc-diagnostics.cc | Loading commit data... | |
| go-gcc.cc | Loading commit data... | |
| go-gcc.h | Loading commit data... | |
| go-lang.c | Loading commit data... | |
| go-linemap.cc | Loading commit data... | |
| go-location.h | Loading commit data... | |
| go-sha1.cc | Loading commit data... | |
| go-system.h | Loading commit data... | |
| gospec.c | Loading commit data... | |
| lang-specs.h | Loading commit data... | |
| lang.opt | Loading commit data... |