On Tue, May 31, 2016 at 7:35 AM, William A Rowe Jr
wrote:
> On May 29, 2016 01:02, "Jie Gao" wrote:
> >
> > Hi All
> >
> > I wonder if anybody is looking at this issue. At the moment, the build
> cores even at the end of generating a Makefile.
> >
> >
Re-sending to include the correct perl.a.o dev list.
On Thu, Apr 14, 2016 at 1:25 PM, William A Rowe Jr
wrote:
> The defect appears to be in t/protocol/TestProtocol/pseudo_http.pm...
>
> First, the handler is registered using
>
> PerlProcessConnectionHandler
The defect appears to be in t/protocol/TestProtocol/pseudo_http.pm...
First, the handler is registered using
PerlProcessConnectionHandler TestProtocol::pseudo_http
so its activities are outside of the request handling phase.
Note that this logic has been broken, for a long time;
We can be more vigilant about unexpectedly null values, however...
how are you running request processing in the connection callback
of mod_perl? That makes no sense, and probably signals a deeper
logic error.
The access checker is configured per-dir, so until the request rec
is completely
r->useragent_addr is assigned on ap_read_request (http_core.c),
called from ap_process_http_(async_)connection
called from process_connection hook (APR_HOOK_REALLY_LAST).
The SEGV occured on process_connection hook, maybe before
ap_process_http_(async_)connection,
#11 0x7fd44f91fd4f in
I wrote the patch for ap_get_useragent_host, but am not familiar
with the details of the report. Researching...
On Wed, Apr 13, 2016 at 5:33 PM, Stefan Fritsch wrote:
> Hi,
>
> I got a report about a new crash in mod_perl tests with 2.4.20:
>
> (gdb) bt
> #0
Hi,
I got a report about a new crash in mod_perl tests with 2.4.20:
(gdb) bt
#0 apr_getnameinfo (hostname=hostname@entry=0x7fd4461ee368,
sockaddr=0x0, flags=flags@entry=0)
at /tmp/buildd/apr-1.5.2/network_io/unix/sockaddr.c:663
#1 0x55feaf0f513a in ap_get_useragent_host