Re: Cobalt deadlock for no apparent reason

2020-01-22 Thread Jan Kiszka via Xenomai
On 22.01.20 11:11, Lange Norbert wrote: -Original Message- From: Jan Kiszka Sent: Dienstag, 21. Jänner 2020 18:46 To: Lange Norbert ; Xenomai (xenomai@xenomai.org) Subject: Re: Cobalt deadlock for no apparent reason NON-ANDRITZ SOURCE: BE CAUTIOUS WITH CONTENT, LINKS OR ATTACHMENTS

RE: Cobalt deadlock for no apparent reason

2020-01-22 Thread Lange Norbert via Xenomai
> -Original Message- > From: Jan Kiszka > Sent: Dienstag, 21. Jänner 2020 18:46 > To: Lange Norbert ; Xenomai > (xenomai@xenomai.org) > Subject: Re: Cobalt deadlock for no apparent reason > > NON-ANDRITZ SOURCE: BE CAUTIOUS WITH CONTENT, LINKS OR > ATTACHMEN

Re: Cobalt deadlock for no apparent reason

2020-01-21 Thread Jan Kiszka via Xenomai
On 20.01.20 19:03, Lange Norbert via Xenomai wrote: Hello, I got a deadlock while running through gdbserver, this is an implementation of a synchronized queue, Fup side waits via condition variable, main wants to push data, but main fails to acquire the mutex. The mutex is an errorchecking

Cobalt deadlock for no apparent reason

2020-01-20 Thread Lange Norbert via Xenomai
Hello, I got a deadlock while running through gdbserver, this is an implementation of a synchronized queue, Fup side waits via condition variable, main wants to push data, but main fails to acquire the mutex. The mutex is an errorchecking type, without priority inheritance, and not used