Just ignore this thread.
I've figured it out.
On Saturday, October 13, 2018 at 12:38:53 PM UTC+2, changkun wrote:
>
> Hi golang nuts:
>
> In "mstart", there is a call "mexit" after "mstart1".
> Howeverm "mstart1" will be entering sched loop and never returns.
>
> So, my question is when will "mexit" be executed? How?
>
> mstart1()
>
> // Exit this thread.
> if GOOS == "windows" || GOOS == "solaris" || GOOS == "plan9" || GOOS ==
> "darwin" || GOOS == "aix" {
> // Window, Solaris, Darwin, AIX and Plan 9 always system-allocate
> // the stack, but put it in _g_.stack before mstart,
> // so the logic above hasn't set osStack yet.
> osStack = true
> }
> mexit(osStack)
>
>
>
>
> https://github.com/golang/go/blob/a5248acd91dcf0e90a68c1ff88ca389dc034557c/src/runtime/proc.go#L1181
>
--
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.
