You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
as is, this isn't as handy as it could as xhyve.Exec never returns anything meaningfull from xhyve since xhyve calls exit / atexit from too many places. this basically means that out of the box whatever we write in goland will end as soon as xhyve dies (so defer, etc turn useless, etc). So, my question is - from your view where is the best place to fix that - upstream in xhyve, by tunneling all exit/atexit calls to its main() function (that we consume) or trap them via this bindings ?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hi,
as is, this isn't as handy as it could as xhyve.Exec never returns anything meaningfull from xhyve since xhyve calls exit / atexit from too many places. this basically means that out of the box whatever we write in goland will end as soon as xhyve dies (so defer, etc turn useless, etc). So, my question is - from your view where is the best place to fix that - upstream in xhyve, by tunneling all exit/atexit calls to its main() function (that we consume) or trap them via this bindings ?
Thanks in advance.
The text was updated successfully, but these errors were encountered: