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

why coffee signal_abort handler invokes after COFFEE_END() ? #44

Open
alexrayne opened this issue May 19, 2020 · 0 comments
Open

why coffee signal_abort handler invokes after COFFEE_END() ? #44

alexrayne opened this issue May 19, 2020 · 0 comments

Comments

@alexrayne
Copy link

alexrayne commented May 19, 2020

work linux 18.04 i386
i got regular crash SIGSEGV that come to coffeee_signal_abort handler after coffee_end()

why this handlers may invokes after them are released?

trace log shows like:

mote7 enter
dump:initialised=0; 
setup for a new handler
installing global signal handlers
installed global signal handlers
installing thread alternative stack
installing thread alternative
installed thread alternative
dump:initialised=1;  reenter=1; ctx=1 
removing thread alternative stack
removed thread alternative stack
removing global signal handlers
removed global signal handlers              <<- this is coffeecatch_handler_cleanup() reports after pthread_key_delete(native_code_thread)
mote7 done                                             <<-- this is application prints after coffee_end()
caught abort sig11
calling old signal handler 
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