Kevin Bracey

The issue is that your build profile pushes the language version up to C++11, but disables GNU extensions, because it's selecting `-std=c++11` not `-std=gnu++11`. Mbed OS should work fine built...

Both mbed os issues linked above have been closed (as "not a bug"), so this should probably be re-opened.

I'm not really in favour of using GNU extensions either, but the Mbed OS build profiles have always had them on for GCC and ARM Compiler, so actually turning them...

First draft - no structural changes attempted. Modifies visible name of `HandlerModeThread` to be `Main` just for this provider, as the thread isn't necessarily in Handler mode, unlike for real...

Actually, there's no option to enable thread support is there, so this will always activate...

Note that this PR is written on the assumption that the changes in #430 have happened - `get_current_id` and `get_actual_current_id` have been collapsed - it's not directly mergeable as is,...

> The Process thread never appeared, even when in an exception handler. Well, if Argon is active, then Bare ARM-M isn't, so you wouldn't ever see the Process thread, no,...

The code is designed so that the Process thread first appears whenever it sees execution stopped on the Process stack (so in a thread, if running Argon). The Process thread...

> Modifications to these registers intentionally or unintentionally by the debugger could result in failures in the process execution context. That's not quite an exception-specific problem. Modifying R4-R11 could cause...

Couple more thoughts - separating the OS threads from the handlers does have its own advantages too. 1) Simplicity - ability to totally ignore the OS's handlers, as if just...