Skip to content

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

@alexrayne

Description

@alexrayne

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 

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions