Hello,
I'm using the Redhat 8 distribution (httpd 2.4.46) and I have a
segmentation fault in mod_proxy_http.c.
How can I work on this? Can I open a bug on bugzilla for a Redhat build?
It does not happen for all requests, just some (and it's reproducible).
Is it possible to deduce the problem from the following stack trace?
> Thread 3 "httpd" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffda59e700 (LWP 3202)]
> ap_proxy_http_prefetch (url=0x7fffcc325dc0
> "/webportalapi/v4/packages", uri=0x7fffcc325c80,
> req=0x7fffcc325ce0) at mod_proxy_http.c:640
> 640 origin->keepalive = AP_CONN_CLOSE;
> (gdb) bt
> #0 ap_proxy_http_prefetch (url=0x7fffcc325dc0
> "/webportalapi/v4/packages", uri=0x7fffcc325c80,
> req=0x7fffcc325ce0) at mod_proxy_http.c:640
> #1 proxy_http_handler (r=0x7fffcc011840, worker=<optimized out>,
> conf=<optimized out>,
> url=0x7fffd8492a6e "http://127.0.0.1/webportalapi/v4/packages",
> proxyname=<optimized out>,
> proxyport=<optimized out>) at mod_proxy_http.c:2076
> #2 0x00007fffeeb84094 in proxy_run_scheme_handler
> (r=r@entry=0x7fffcc011840, worker=0x5555f8139920,
> conf=conf@entry=0x5555f8139778, url=0x7fffd8492a6e
> "http://127.0.0.1/webportalapi/v4/packages",
> proxyhost=proxyhost@entry=0x0, proxyport=proxyport@entry=0) at
> mod_proxy.c:3102
> #3 0x00007fffeeb84e49 in proxy_handler (r=0x7fffcc011840) at
> mod_proxy.c:1266
> #4 0x000055555559cad8 in ap_run_handler (r=r@entry=0x7fffcc011840) at
> config.c:170
> #5 0x000055555559d096 in ap_invoke_handler (r=r@entry=0x7fffcc011840)
> at config.c:444
> #6 0x00005555555b4243 in ap_process_async_request
> (r=r@entry=0x7fffcc011840) at http_request.c:453
> #7 0x00005555555b43b2 in ap_process_request
> (r=r@entry=0x7fffcc011840) at http_request.c:488
> #8 0x00005555555b05d5 in ap_process_http_sync_connection
> (c=0x7fffd4003c68) at http_core.c:210
> #9 ap_process_http_connection (c=0x7fffd4003c68) at http_core.c:251
> #10 0x00005555555a6ab8 in ap_run_process_connection
> (c=c@entry=0x7fffd4003c68) at connection.c:42
> #11 0x00005555555a7038 in ap_process_connection
> (c=c@entry=0x7fffd4003c68, csd=csd@entry=0x7fffd4003a50) at
> connection.c:219
> #12 0x00007ffff392b41f in process_socket (bucket_alloc=0x7fffcc000b88,
> my_thread_num=0, my_child_num=0,
> sock=0x7fffd4003a50, p=0x7fffd40039d8, thd=0x5555566286a0) at
> worker.c:479
> #13 worker_thread (thd=0x5555566286a0, dummy=<optimized out>) at
> worker.c:808
> #14 0x00007ffff6b0a14a in start_thread (arg=<optimized out>) at
> pthread_create.c:479
> #15 0x00007ffff6635dc3 in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thanks a lot
I'm using the Redhat 8 distribution (httpd 2.4.46) and I have a
segmentation fault in mod_proxy_http.c.
How can I work on this? Can I open a bug on bugzilla for a Redhat build?
It does not happen for all requests, just some (and it's reproducible).
Is it possible to deduce the problem from the following stack trace?
> Thread 3 "httpd" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffda59e700 (LWP 3202)]
> ap_proxy_http_prefetch (url=0x7fffcc325dc0
> "/webportalapi/v4/packages", uri=0x7fffcc325c80,
> req=0x7fffcc325ce0) at mod_proxy_http.c:640
> 640 origin->keepalive = AP_CONN_CLOSE;
> (gdb) bt
> #0 ap_proxy_http_prefetch (url=0x7fffcc325dc0
> "/webportalapi/v4/packages", uri=0x7fffcc325c80,
> req=0x7fffcc325ce0) at mod_proxy_http.c:640
> #1 proxy_http_handler (r=0x7fffcc011840, worker=<optimized out>,
> conf=<optimized out>,
> url=0x7fffd8492a6e "http://127.0.0.1/webportalapi/v4/packages",
> proxyname=<optimized out>,
> proxyport=<optimized out>) at mod_proxy_http.c:2076
> #2 0x00007fffeeb84094 in proxy_run_scheme_handler
> (r=r@entry=0x7fffcc011840, worker=0x5555f8139920,
> conf=conf@entry=0x5555f8139778, url=0x7fffd8492a6e
> "http://127.0.0.1/webportalapi/v4/packages",
> proxyhost=proxyhost@entry=0x0, proxyport=proxyport@entry=0) at
> mod_proxy.c:3102
> #3 0x00007fffeeb84e49 in proxy_handler (r=0x7fffcc011840) at
> mod_proxy.c:1266
> #4 0x000055555559cad8 in ap_run_handler (r=r@entry=0x7fffcc011840) at
> config.c:170
> #5 0x000055555559d096 in ap_invoke_handler (r=r@entry=0x7fffcc011840)
> at config.c:444
> #6 0x00005555555b4243 in ap_process_async_request
> (r=r@entry=0x7fffcc011840) at http_request.c:453
> #7 0x00005555555b43b2 in ap_process_request
> (r=r@entry=0x7fffcc011840) at http_request.c:488
> #8 0x00005555555b05d5 in ap_process_http_sync_connection
> (c=0x7fffd4003c68) at http_core.c:210
> #9 ap_process_http_connection (c=0x7fffd4003c68) at http_core.c:251
> #10 0x00005555555a6ab8 in ap_run_process_connection
> (c=c@entry=0x7fffd4003c68) at connection.c:42
> #11 0x00005555555a7038 in ap_process_connection
> (c=c@entry=0x7fffd4003c68, csd=csd@entry=0x7fffd4003a50) at
> connection.c:219
> #12 0x00007ffff392b41f in process_socket (bucket_alloc=0x7fffcc000b88,
> my_thread_num=0, my_child_num=0,
> sock=0x7fffd4003a50, p=0x7fffd40039d8, thd=0x5555566286a0) at
> worker.c:479
> #13 worker_thread (thd=0x5555566286a0, dummy=<optimized out>) at
> worker.c:808
> #14 0x00007ffff6b0a14a in start_thread (arg=<optimized out>) at
> pthread_create.c:479
> #15 0x00007ffff6635dc3 in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thanks a lot