On Sun, Jun 27, 2010 at 15:18, Nicholas Clark <[email protected]> wrote: > On Sat, Jun 26, 2010 at 04:37:17PM -0600, Alex Hunsaker wrote:
>> So it smells like some kind of corruption to me. If I run it under valgrind: >> ==27940== Invalid read of size 4 >> ==27940== at 0x4A52F84: modperl_perl_call_list (modperl_util.c:479) >> I dont have any idea _why_. Ring any bells ? > > No, but by inspection: > On reflection, I think that this *is* a bug in mod_perl, as they're going > to get tripped up in similar fashion if any code run as part of an END block > contains a string eval containing an END block. Yep! If I switch that over to use Perl_call_list() (note, i have not looked *to* closely to make sure it does the right thing for mod_perl) instead of it using its own builtin thing everything seems to work! > This list, obviously, isn't the right place to report bugs in mod_perl. Yeah, ill go post a report on that list (tomorrow) and point back to this thread. Course feel free to beat me to the punch :-). Thanks! -- You've received this message because you are subscribed to the Devel::NYTProf Development User group. Group hosted at: http://groups.google.com/group/develnytprof-dev Project hosted at: http://perl-devel-nytprof.googlecode.com CPAN distribution: http://search.cpan.org/dist/Devel-NYTProf To post, email: [email protected] To unsubscribe, email: [email protected]
