apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Orton <jor...@redhat.com>
Subject Re: [Fwd: [mp2] coredump strerror code on Solaris 8
Date Wed, 08 Sep 2004 21:31:05 GMT
On Wed, Sep 08, 2004 at 05:01:33PM -0400, Stas Bekman wrote:
> Here is another:
> 
> (gdb) bt
> #0  apr_cpystrn (dst=0xffbef010 "", src=0x0, dst_size=4290703375)
>    at apr_cpystrn.c:57
> #1  0xff1d4c4c in stuffbuffer (buf=0xffbeef10 "", bufsize=256, s=0x0)
>    at errorcodes.c:34
> #2  0xfee074f0 in modperl_error_strerror (rc=500) at modperl_error.c:37
> #3  0xfe990c90 in XS_APR__Error_strerror (cv=0x1f4) at Error.xs:36
> 
> In the second one the trace seems to be optimized away, since 
> modperl_error_strerror does not call stuffbuffer, so it's some internal 
> function that is broken.

Three cheers for tail call recursion...  I guess mod_perl_error_strerror
will call apr_strerror(500, buf, 256) in this case?  Bets are 500 is an
HTTP status code rather than a genuine apr_status_t so you probably
didn't really want to do that, but it probably shouldn't segfault
either.

joe

Mime
View raw message