crasbe

With your proposed solution, wouldn't the mutex be double-freed in line 578 if everything goes successfully? When two threads are running, this could accidentally free the mutex from another thread...

@jia200x you can restart failed Murdock build jobs in the CI as well: Either click on the small arrow on the right and select "Restart"... ...or click on the circular...

On my machine the `tests/socker_zep` fails with a SegFault with and without `llvm` alike Build Logs ``` buechse@skyleaf:~/RIOTstuff/riot-vanillaice/RIOT$ make BOARD=native64 TOOLCHAIN=llvm -C tests/net/socket_zep all test make: Entering directory '/home/buechse/RIOTstuff/riot-vanillaice/RIOT/tests/net/socket_zep' Building...

Yes, this looks good. I had something similar in mind, but I wasn't able to articulate a proper proposal. 👍

Perhaps for the SVC we could also modify it like this: ```c typedef void (*svc_dispatch_handler_t)(unsigned int svc_number, unsigned int *svc_args); svc_dispatch_handler_t _svc_dispatch_handler = NULL; ... switch (svc_number) { case 1:...

The code looks good, but I don't have any hardware to test this. Perhaps @mguetschow has access to that? You can squash the commits in the meantime.

It was actually surprisingly difficult to get such an old version of GCC running. I did not find a package for it in the Launchpad, so I used the package...

I had to update the Dockerfile to include `newlib` so it actually builds: ``` root@6ae9012a2c0d:/workspace/RIOT# BOARD=nrf52840dk make -C examples/basic/hello-world/ -j make: Entering directory '/workspace/RIOT/examples/basic/hello-world' Building application "hello-world" for "nrf52840dk" with...

Depending on how much time @maribu wants to (or would have to) invest into this, we could also just exclude GCC < 10 for `mpaland-printf`. Not the nicest solution, but...