Arshavir Grigorian wrote:

I'd appreciate if you could work with the debugger and figure out the real trace it has taken to help us debug it, as suggested in the previous reply.



It looks like the control is going into the first branch of the if statement calling native_strerror (statcode=500, buf=0xffbeef10 "", bufsize=256).

Here is a new backtrace:

#0 0xff2a7fec in apr_cpystrn (dst=0xffbeee90 "ï\001", src=0x0, dst_size=256)
at apr_cpystrn.c:57
57 if (!(*d = *src)) {
(gdb) where
#0 0xff2a7fec in apr_cpystrn (dst=0xffbeee90 "ï\001", src=0x0, dst_size=256)
at apr_cpystrn.c:57
#1 0xff2c0f18 in stuffbuffer (buf=0xffbeee90 "ï\001", bufsize=256, s=0x0)
at errorcodes.c:34
#2 0xff2c18e8 in native_strerror (statcode=-4264304,
buf=0x100 <Address 0x100 out of bounds>, bufsize=0) at errorcodes.c:375
(gdb)


Hope that's useful.

Well, this seems to be a totally different trace. What I was asking is to work interactively with the gdb debugger and see where it goes wrong. I've submitted your traces to the apr-dev list. Hopefully someone will know what's going on.



-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com

--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to