A question to the more experienced httpd debuggers: In regard to https://bz.apache.org/bugzilla/show_bug.cgi?id=58524
Can I recover any files/lines from these ======= Backtrace: ========= /lib64/libc.so.6[0x32a507174f] /lib64/libc.so.6(cfree+0x4b)[0x32a5075a4b] /opt/appl/apr-1.5.2/lib/libapr-1.so.0(apr_allocator_destroy+0x1b)[0x2abbed566e6b] /opt/appl/httpd/modules/mod_http2.so[0x2abbf10e082e] /opt/appl/httpd/modules/mod_http2.so[0x2abbf10e32ee] /opt/appl/httpd/modules/mod_http2.so[0x2abbf10db00a] /opt/appl/httpd/modules/mod_http2.so[0x2abbf10db233] /opt/appl/httpd/modules/mod_http2.so[0x2abbf10de351] /opt/appl/httpd-2.4.17/bin/httpd(ap_run_process_connection+0x4a)[0x456efa] /opt/appl/httpd-2.4.17/bin/httpd[0x468fa0] /lib64/libpthread.so.0[0x32a5c0683d] /lib64/libc.so.6(clone+0x6d)[0x32a50d526d] ======= Memory map: ======== or do I have to ask the user to run a -g version and report on that? High load wreckage in production, always tricky... Thanks, Stefan
