Le 29/03/2019 à 23:57, Yann Ylavic a écrit :
On Fri, Mar 29, 2019 at 10:53 PM Marion & Christophe JAILLET
<[email protected]> wrote:
Could others confirm that they have tested with 'prefork' and that they
don't have any issue?
No issue here with the somewhat similar Debian 10 / gcc-8.3 /
libssl-1.1.1b. I don't have my older Debian(s) at hand as of now to
test multiple times like a just did with Debian 10, but I tested
prefork on them at least once yesterday with no issue either...
What the core files say?
For some unknown (and forgotten) reason, I was using -DNO_USE_SIGACTION
when calling ./configure.
I've removed it, re-confed, re-builf, re-tested:
t/modules/ratelimit.t ............... 1/3 [ error] oh jeez, server
dumped core
[ error] for stacktrace, run: gdb /home/tititou36/httpd-2.4/bin/httpd
-core /home/tititou36/svn_test_framework/t/core
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Aucun fichier ou dossier de ce
type.
t/TEST t/ssl/
t/ssl/varlookup.t .. 81/83 [ error] oh nuts, server dumped core
[ error] for stacktrace, run: gdb /home/tititou36/httpd-2.4/bin/httpd
-core /home/tititou36/svn_test_framework/t/core
with same kind of code dump.
I won't investigate further for now.
CJ
