Re: www/apache-httpd segfaults

2016-01-16 Thread David CARLIER
bug reproduced, happens pretty quickly once I stressed httpd2 with siege ... On 16 January 2016 at 19:48, Pedro de Oliveira wrote: > Ignore what I said in the earlier email about "mpm_prefork", I wasnt > using it. Sorry. > > It still crashes after a few requests. This is the backtrace from > apac

Re: www/apache-httpd segfaults

2016-01-16 Thread Pedro de Oliveira
Ignore what I said in the earlier email about "mpm_prefork", I wasnt using it. Sorry. It still crashes after a few requests. This is the backtrace from apache build with -O0 and -ggdb. # gdb --args httpd2 -X (gdb) run Starting program: /usr/local/sbin/httpd2 -X ... Program received signal SIGSEGV

Re: www/apache-httpd segfaults

2016-01-16 Thread Michael McConville
Pedro de Oliveira wrote: > Following your tips I built Apache with -O0 and the segfaults in > "mpm_prefork" no longer happen. Maybe its a gcc optimization issue. I > dont know which -O OpenBSD uses by default, but I will try it also > with -O1 and report back. Remember, compiler optimizations can

Re: www/apache-httpd segfaults

2016-01-16 Thread Pedro de Oliveira
Hello, Following your tips I built Apache with -O0 and the segfaults in "mpm_prefork" no longer happen. Maybe its a gcc optimization issue. I dont know which -O OpenBSD uses by default, but I will try it also with -O1 and report back. Now that it doesnt crash I fiddled a bit more with http2. # g

Re: www/apache-httpd segfaults

2016-01-15 Thread Stuart Henderson
I've disabled mod_http2 from being packaged for now, not sure how to debug it further at present. On 2016/01/14 18:58, Pedro de Oliveira wrote: > Hi there, > > Yesterday I was trying to play with the http2 module on Apache from > ports, as I saw it was added to the ports file list. The problem i

www/apache-httpd segfaults

2016-01-14 Thread Pedro de Oliveira
Hi there, Yesterday I was trying to play with the http2 module on Apache from ports, as I saw it was added to the ports file list. The problem is that the module isnt working correctly. If you try it on a http vhost, it simply returns the page via the normal way (http). And if you enable it on a