Mit obigen Patch von Wirbel bleibt nur noch eine Warnung:
g++ -g -O1 -Wall -march=goldmont-plus -Woverloaded-virtual -Wno-parentheses -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -std=c++11 -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"vnsiserver"' -DVNSI_SERVER_VERSION='"1.8.
3"' -I/usr/src/packages/BUILD/vdr-2.6.6-test/include -o vnsitimer.o vnsitimer.c
In file included from /usr/include/c++/13/bits/shared_ptr_atomic.h:33,
from /usr/include/c++/13/memory:81,
from videoinput.h:27,
from videoinput.c:27:
In member function ‘std::__atomic_base<_IntTp>::__int_type std::__atomic_base<_IntTp>::load(std::memory_order) const [with _ITp = bool]’,
inlined from ‘std::atomic<bool>::operator bool() const’ at /usr/include/c++/13/atomic:87:26,
inlined from ‘bool cDummyReceiver::BeenDetached()’ at videoinput.c:428:32,
inlined from ‘static std::shared_ptr<cDummyReceiver> cDummyReceiver::Create(cDevice*)’ at videoinput.c:469:28:
/usr/include/c++/13/bits/atomic_base.h:505:31: warning: ‘unsigned char __atomic_load_1(const volatile void*, int)’ writing 1 byte into a region of size 0 overflows the destination [-Wstringop-overflow=]
505 | return __atomic_load_n(&_M_i, int(__m));
| ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~
In static member function ‘static std::shared_ptr<cDummyReceiver> cDummyReceiver::Create(cDevice*)’:
cc1plus: note: destination object is likely at address zero
ich gabe diesmal wie zu erkennen ist die Compileroptionen angepasst. Wie oben von SHF angeregt. DEBUG_LOCKING ist aus
)