Ilya Shipitsin

have a look https://travis-ci.org/chipitsine/openvpn-gui/jobs/230523093#L1469 and https://travis-ci.org/chipitsine/openvpn-gui/jobs/230527072#L1629 as I had a look at windres sources, it is ... designed to compile any resource file, if possible with warning, but not fail....

if we convert rc into "visual studio compatible", we can run VS under appveyor

I'll ask at binutils/windres community. Maybe we just miss something obvious

surprise, windres does fail on its own (i.e. fails as expected), on the same "kr" resource https://travis-ci.org/chipitsine/windres-xprmnts/jobs/231258891#L1258 it seems to fail ... when including files ?

not sure Azure DevOps allows scheduled builds. I need to have a look :) there are about 10 builds a day in general. no need to kick coverity on each...

@Tristan971 , macos github runners are expensive compared to linux due to hardware reasons. can we close this issue since [Cross Compile](https://github.com/haproxy/haproxy/actions/runs/4474095355) run on linux ?

in `ssl_sock_handshake` we invoke `conn_get_ssl_sock_ctx` which compares conn against NULL. thus gcc assumes conn might be NULL. after that we invoke `conn_ctrl_ready` without prior check for NULL ``` static int...

can we address first and second finding ?

after I masked out 3rd detection, another detection revealed ``` cc1: all warnings being treated as errors make: *** [Makefile:982: src/ssl_ckch.o] Error 1 src/ssl_sock.c: In function ‘ssl_sock_io_cb’: src/ssl_sock.c:6241:41: error: dereference...

I use gcc from master branch. However, static analyzer did not change a lot from gcc-12.X ``` #!/bin/bash export CC=/home/ilia/gcc/gcc-home/bin/gcc make clean make TARGET=linux-glibc USE_OPENSSL=1 DEBUG_CFLAGS="-fanalyzer" ```