Skip to content

No way to terminate #6

Description

@ProExpertProg

I think a common use of this will be a main function (mbed_start) that will spin up some RTOS stuff, wait for some time/wait for the tests to finish, and then exit everything. We could provide a "graceful shutdown function" that will either 1. join all threads but idle and exit, or 2. exit all functions and do stack unwinding (as well as deallocate the thread structures).

Alternatively, because the stack gets unwinded when exit is called, we could just clean up in the destructor of ThreadDispatcher, which is allocated statically and will hence be destroyed (I think - Valgrind only says that pthread memory is leaked).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions