Hi,
this patch solved the file_close segfault. Never saw that again.
Right now i got this one:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f129f612274 in pthread_mutex_lock () from
/lib/x86_64-linux-gnu/libpthread.so.0
(gdb) bt
#0 0x00007f129f612274 in pthread_mutex_lock () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1 0x00007f129fe83bc9 in apr_thread_mutex_lock (mutex=<optimized out>)
at locks/unix/thread_mutex.c:92
#2 0x00007f129fe82712 in apr_file_seek
(thefile=thefile@entry=0x7f120c0670c0, where=where@entry=0,
offset=offset@entry=0x7f12897f9b60) at file_io/unix/seek.c:62
#3 0x00000000004dc413 in read_to_scratch (b=0x7f11c807ea08,
io=0x7f11c80806d8) at h2_conn_io.c:220
#4 h2_conn_io_pass (io=io@entry=0x7f11c80806d8, bb=0x7f11c8080a08) at
h2_conn_io.c:434
#5 0x00000000004ca3ae in on_send_data_cb (ngh2=<optimized out>,
frame=<optimized out>, framehd=<optimized out>, length=1291,
source=<optimized out>, userp=0x7f11c8080690) at h2_session.c:649
#6 0x00007f12a0980e95 in ?? () from
/usr/lib/x86_64-linux-gnu/libnghttp2.so.14
#7 0x00007f12a0981ea9 in nghttp2_session_send () from
/usr/lib/x86_64-linux-gnu/libnghttp2.so.14
#8 0x00000000004cca89 in h2_session_send (session=0x7f11c8080690) at
h2_session.c:1414
#9 0x00000000004cfc8c in h2_session_process (session=0x7f11c8080690,
async=1) at h2_session.c:2246
#10 0x00000000004bf641 in h2_conn_run (ctx=0x7f120c066730,
c=0x7f128c06cd98) at h2_conn.c:214
#11 0x00000000004c202a in h2_h2_process_conn (c=0x3732323535395f39) at
h2_h2.c:658
#12 0x000000000046a450 in ap_run_process_connection (c=0x7f128c06cd98)
at connection.c:42
#13 0x00000000004fbf10 in process_socket (my_thread_num=<optimized out>,
my_child_num=<optimized out>, cs=0x7f128c06cd08,
sock=<optimized out>, p=<optimized out>, thd=<optimized out>) at
event.c:1134
#14 worker_thread (thd=0x3732323535395f39, dummy=0x0) at event.c:2137
#15 0x00007f129f6100a4 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#16 0x00007f129f14162d in clone () from /lib/x86_64-linux-gnu/libc.so.6
Stefan
Am 20.01.2017 um 18:17 schrieb Yann Ylavic:
> On Fri, Jan 20, 2017 at 5:51 PM, Stefan Priebe - Profihost AG
> <s.pri...@profihost.ag> wrote:
>> Yes. Until now I got 4 traces. But all are the same pointing to apr kill
>> pool. Not like before where i got many different ones.
>
> Could you try this new patch on mod_http2 please?
>
> Thanks,
> Yann.
>
