Sorry misstyped it's V7 with mod_http 1.8.8 unpatched. Stefan
Excuse my typo sent from my mobile phone. > Am 20.01.2017 um 16:23 schrieb Stefan Priebe - Profihost AG > <s.pri...@profihost.ag>: > > Hi, > > it crashed again with V6 and plain mod_http2 v1.8.8. > > This is the crash incl. line numbers: > Program terminated with signal SIGSEGV, Segmentation fault. > #0 apr_pool_cleanup_kill (p=0x2d392d3333322d32, > data=data@entry=0x7f330006bc70, > cleanup_fn=cleanup_fn@entry=0x7f33155b0f90 <apr_unix_file_cleanup>) > at memory/unix/apr_pools.c:2264 > 2264 memory/unix/apr_pools.c: No such file or directory. > (gdb) bt > #0 apr_pool_cleanup_kill (p=0x2d392d3333322d32, > data=data@entry=0x7f330006bc70, > cleanup_fn=cleanup_fn@entry=0x7f33155b0f90 <apr_unix_file_cleanup>) > at memory/unix/apr_pools.c:2264 > #1 0x00007f33155b5e51 in apr_pool_cleanup_run (p=<optimized out>, > data=0x7f330006bc70, > cleanup_fn=0x7f33155b0f90 <apr_unix_file_cleanup>) at > memory/unix/apr_pools.c:2342 > #2 0x00007f33155b1322 in apr_file_close (file=<optimized out>) at > file_io/unix/open.c:255 > #3 0x00000000004d0012 in stream_pool_cleanup (ctx=0x7f3294022480) at > h2_stream.c:182 > #4 0x00007f33155b4b1e in run_cleanups (cref=<optimized out>) at > memory/unix/apr_pools.c:2352 > #5 apr_pool_destroy (pool=0x7f3294022408) at memory/unix/apr_pools.c:814 > #6 0x00000000004d0786 in h2_stream_destroy (stream=<optimized out>) at > h2_stream.c:249 > #7 0x00000000004c334c in stream_done (m=<optimized out>, > stream=<optimized out>, rst_error=<optimized out>) at h2_mplx.c:470 > #8 0x00000000004c335b in stream_done_iter (ctx=<optimized out>, > val=<optimized out>) at h2_mplx.c:475 > #9 0x00007f33155ac156 in apr_hash_do (comp=comp@entry=0x4d5880 > <ihash_iter>, rec=rec@entry=0x7f32f7feea50, ht=<optimized out>) > at tables/apr_hash.c:542 > #10 0x00000000004d623d in h2_ihash_iter (ih=<optimized out>, > fn=fn@entry=0x4c3350 <stream_done_iter>, ctx=ctx@entry=0x7f3294034c88) > at h2_util.c:315 > #11 0x00000000004c4649 in h2_mplx_release_and_join (m=0x7f3294034c88, > wait=0x7f3294034c30) at h2_mplx.c:579 > #12 0x00000000004ca7cf in h2_session_destroy (session=0x7f3294034a50) at > h2_session.c:739 > #13 0x000000000045b726 in remove_empty_buckets (bb=0x7f330006af18) at > core_filters.c:720 > #14 0x000000000045be28 in setaside_remaining_output (f=0x7f32ec0c5b88, > ctx=0x7f32ec0c5e48, bb=0x7f330006af18, c=<optimized out>, > c=<optimized out>) at core_filters.c:584 > #15 0x000000000045c896 in ap_core_output_filter (f=0x2d392d3333322d32, > new_bb=0x7f330006af18) at core_filters.c:568 > #16 0x00000000004ad932 in ssl_io_filter_output (f=0x7f330006aed0, > bb=0x7f32ec0c5f10) at ssl_engine_io.c:1716 > #17 0x00000000004aad0a in ssl_io_filter_coalesce (f=0x2d392d3333322d32, > bb=0x7f32ec0c5f10) at ssl_engine_io.c:1663 > #18 0x00000000004db543 in pass_output (io=0x7f3294034a98, > session_eoc=0x7f3294034a50, flush=<optimized out>) at h2_conn_io.c:311 > #19 0x00000000004cf50a in h2_session_process (session=0x7f3294034a50, > async=1) at h2_session.c:2347 > #20 0x00000000004befb2 in h2_conn_run (ctx=0x7f32ec0c5e18, > c=0x7f330006a958) at h2_conn.c:214 > #21 0x00000000004c198a in h2_h2_process_conn (c=0x2d392d3333322d32) at > h2_h2.c:658 > #22 0x000000000046a2b0 in ap_run_process_connection (c=0x7f330006a958) > at connection.c:42 > #23 0x00000000004fb890 in process_socket (my_thread_num=<optimized out>, > my_child_num=<optimized out>, cs=0x7f330006a8c8, > sock=<optimized out>, p=<optimized out>, thd=<optimized out>) at > event.c:1134 > #24 worker_thread (thd=0x2d392d3333322d32, dummy=0x7f330006bc70) at > event.c:2137 > #25 0x00007f3314d400a4 in start_thread () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #26 0x00007f331487162d in clone () from /lib/x86_64-linux-gnu/libc.so.6 > > Stefan >> Am 20.01.2017 um 13:20 schrieb Stefan Eissing: >> Please without. Then I least know if that version behaves. Planning on more >> extensive changes for a 1.9.0 now. Thanks! >> >> -Stefan >> >>> Am 20.01.2017 um 13:18 schrieb Stefan Priebe - Profihost AG >>> <s.pri...@profihost.ag>: >>> >>> Will start retesting V6 patch. Should I use mod_http2 1.8.8 with or without >>> patches? >>> >>> Greets, >>> Stefan >>> >>> Excuse my typo sent from my mobile phone. >>> >>>> Am 20.01.2017 um 13:04 schrieb Stefan Eissing >>>> <stefan.eiss...@greenbytes.de>: >>>> >>>> Different apr versions? Might there have been a bugfix affecting us? >>>> >>>>> Am 20.01.2017 um 12:49 schrieb Stefan Priebe - Profihost AG >>>>> <s.pri...@profihost.ag>: >>>>> >>>>> might this be a debian bug? i can't reproduce with apr-included. >>>>> >>>>>> Am 20.01.2017 um 08:20 schrieb Yann Ylavic: >>>>>> Hi, >>>>>> >>>>>> On Fri, Jan 20, 2017 at 8:03 AM, Stefan Priebe - Profihost AG >>>>>> <s.pri...@profihost.ag> wrote: >>>>>>> Hi Stefan, >>>>>>> >>>>>>>> Am 19.01.2017 um 22:44 schrieb Stefan Eissing: >>>>>>>> this seems to be a tough bone to chew. Therefore we need to go deeper: >>>>>>>> - can you compile the module so that we see line numbers in the trace? >>>>>>> >>>>>>> Do you have any idea how to arrange this? I've no idea how to pass the >>>>>>> -ggdb option through Apache. >>>>>> >>>>>> DEB_CFLAGS_SET="-O2 -ggdb -fno-strict-aliasing ..." dpkg-buildpackage ... >>>>>> >>>>>>> >>>>>>>> - which apr version are you using? >>>>>>> this one: >>>>>>> https://packages.debian.org/jessie/libapr1 >>>>>> >>>>>> Could you also build libapr1 with this same flags? >>>>>> >>>> >>>> Stefan Eissing >>>> >>>> <green/>bytes GmbH >>>> Hafenstrasse 16 >>>> 48155 Münster >>>> www.greenbytes.de >>>> >> >> Stefan Eissing >> >> <green/>bytes GmbH >> Hafenstrasse 16 >> 48155 Münster >> www.greenbytes.de >>
