> Kirinn via fpc-devel hat am 22. August 2020
> um 03:50 geschrieben:
>
> For set/reset counting we'd need a semaphore instead of an RTL event,
> but I don't think we have an actively supported semaphore implementation
> at this time.
I can provide one. If you like to, i can send the source f
When I researched synchronisation behavior and wrote the wiki page
"Threads", I found that RTL events behave like this:
- When the event is set, a single waiting thread is released (in FIFO
order), and the event is automatically immediately reset.
- The event can only be in a set or unset sta
I am tracing a race condition in lazCollections TLazThreadedQueue
on win-64
What is supposed to happen in the following case:
2 or more threads are waiting on the some event
RTLeventWaitFor(UniqueEvent)
1 thread sets it
RTLeventSetEvent(UniqueEvent)
I expect that wakes up exactly ONE threa
On Sat, 22 Aug 2020, baldzhang via fpc-devel wrote:
certificate verify issue of tfphttpclient with openssl
patch file attached,
some explain:
a) sslsockets.pp
the TVerifyCertificateEvent shall allow to modify the "Allow" param, for
compatibility reason,
function DoVerifyCert: Boolean may
certificate verify issue of tfphttpclient with openssl
from wiki page, https client as easy as:
tfphttpclient.simpleget('https://192.168.0.1')
in TOpenSSLSocketHandler, the VerifyPeerCert is False by default
when check the TSSL.VerifyResult, will got one of following:
1) X509_V_ERR_DEPTH_ZERO_
Another strange "not inline warning"
All marked as inline
Implementation code of Some is first, then Bar, then FOo. So all code is
known,when needed.
Foo => Bar => Some
Bar compiles without warning. So I guess Some was inlined
Foo gives a warning. But it warns that "Some is not inlined"
Does
