Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question regarding exit traps #1

Open
AntonioMeireles opened this issue Aug 25, 2015 · 0 comments
Open

question regarding exit traps #1

AntonioMeireles opened this issue Aug 25, 2015 · 0 comments

Comments

@AntonioMeireles
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant