priority order violation Topic is solved

[wurstnase]

Hi,

I just saw an issue with a "priority order violation" after an unlock.

My code looks like:

Code: Select all

chSysLock();
chEvtBroadcastFlagsI(&menu_es, 0);
chMtxUnlockAllS();
chSysUnlock();

Shouldn't the chMtxUnlockAllS() reschedule in any case?
I was stepping with the debugger in a second thread while this occur.

[Giovanni]

Hi,

Good point, it should.

chMtxUnlockAll() uses it internally and then reschedules explicitly, this should not be required.

I was going to release 20.3.0, this will be fixed in 20.3.1.

Giovanni

[Giovanni]

Hi,

Fixed as bug #1076.

Giovanni