Beat Küng c46274043f printload: use sched_lock to protect access to tcb ...

what could have gone wrong before? A scheduling switch during the printload
could have led to a task exit, rendering the tcb invalid. After switching
back, printload would access invalid memory.

This keeps the sched_lock() section as small as possible, just grabbing the
tcb variables we need.

2017-04-01 20:19:52 +02:00

..

drivers

fmuv5:cr2 was written to cr1

2017-04-01 11:37:47 +02:00

examples

avoid double promotions

2017-04-01 20:19:28 +02:00

firmware

Fix UAVCAN bootloader builds broken by os calls from stm32_flash

2017-03-24 16:22:47 +01:00

include

visibility.h: add #pragma GCC poison getenv setenv putenv

2017-03-29 23:02:09 +02:00

lib

avoid double promotions

2017-04-01 20:19:28 +02:00

modules

printload: use sched_lock to protect access to tcb

2017-04-01 20:19:52 +02:00

platforms

systemlib/visibility.h: remove this file

2017-03-29 23:02:09 +02:00

systemcmds

avoid double promotions

2017-04-01 20:19:28 +02:00

mainpage.dox

Merged beta into mavlink rework branch

2014-01-28 15:13:14 +01:00