Re: [vdr] [PATCH] Add thread safety to cRingBufferLinear

2023-02-02 Thread patrick9876
On 02/02/2023 23:27, Klaus Schmidinger wrote: On 02.02.23 23:16, Patrick Lerda wrote: Beside preventing crashes with vdr-2.6.3 this is required to get vdr to work properly with the gcc thread sanitizer. cRingBufferLinear was designed to be thread safe without locking. What "crashes with vdr-2.

Re: [vdr] [PATCH] Add thread safety to cRingBufferLinear

2023-02-02 Thread Klaus Schmidinger
On 02.02.23 23:16, Patrick Lerda wrote: Beside preventing crashes with vdr-2.6.3 this is required to get vdr to work properly with the gcc thread sanitizer. cRingBufferLinear was designed to be thread safe without locking. What "crashes with vdr-2.6.3" are you referring to? Klaus ___

[vdr] [PATCH] Add thread safety to cRingBufferLinear

2023-02-02 Thread Patrick Lerda
Beside preventing crashes with vdr-2.6.3 this is required to get vdr to work properly with the gcc thread sanitizer. --- ringbuffer.c | 18 +- ringbuffer.h | 3 +++ 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/ringbuffer.c b/ringbuffer.c index 902c887..1c24df2 10

[vdr] [PATCH] Fix cThread related race conditions

2023-02-02 Thread Patrick Lerda
This change fixes the following issue: ==15457==ERROR: AddressSanitizer: SEGV on unknown address 0x02d0 (pc 0x7fd2f4301710 bp 0x7fd2b5552a30 sp 0x7fd2b5552988 T228) ==15457==The signal is caused by a READ memory access. ==15457==Hint: address points to the zero page. #0 0x7fd2f4301710