There are several conditions that bypass recover. Another example is "fatal
error: concurrent map read and map write". The error messages typically
start with "fatal error" and represent a non recoverable exception in the
run time rather than a user defined condition.
I don't know the official term for these exceptions. My team has been
calling them "super panic" to distinguish them from actual calls to panic.
On Jan 4, 2019 09:43, "伊藤和也" <kazya.ito.dr...@gmail.com> wrote:
I tried to recover a stack overflow but I couldn't.
func main() {
defer func() {
src := recover()
fmt.Println(src)
}()
main()
}
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
