perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Hay <steve....@uk.radan.com>
Subject Problem with mp1 + bleadperl on Win32
Date Mon, 17 Jul 2006 14:19:59 GMT
[No luck with this on p5p, so I'm trying here instead...]

During the course of upgrading my development machine from perl-5.8.8 to 
bleadperl, I've found that mod_perl-1.29 (with apache-1.3.36) is now not 
happy.

It built OK, but when testing it crashes here in t/modules/constants.t:

Perl_pp_entersub() line 2833 + 11 bytes
Perl_runops_debug() line 1819 + 9 bytes
Perl_call_sv(sv * 0x00bb1458, long 4) line 2641
perl_call_handler(sv * 0x00bb1458, request_rec * 0x00a43228, av * 
0x00000000) line 1668 + 11 bytes
perl_run_stacked_handlers(char * 0x1007b048 `string', request_rec * 
0x00a43228, av * 0x00ae5e78) line 1381 + 15 bytes
perl_handler(request_rec * 0x00a43228) line 904 + 182 bytes
ap_invoke_handler(request_rec * 0x00a43228) line 475 + 10 bytes
process_request_internal(request_rec * 0x00a43228) line 1298 + 9 bytes
ap_process_request(request_rec * 0x00a43228) line 1314 + 9 bytes
child_sub_main(int 7) line 6164
child_main(int 7) line 6234 + 9 bytes
_threadstartex(void * 0x009fb7a8) line 212 + 13 bytes
KERNEL32! 7c80b50b()

pp_hot.c line 2833 is:

PAD_SET_CUR_NOSAVE(padlist, CvDEPTH(cv));

and I see that padlist is NULL, which causes the crash (an access 
violation).

I'm running on Win32.  Can somebody on a saner OS try this and see if it 
crashes for them?


------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are confidential
and intended for the addressee(s) only. If you have received this message in error or there
are any problems, please notify the sender immediately. The unauthorized use, disclosure,
copying or alteration of this message is strictly forbidden. Note that any views or opinions
presented in this email are solely those of the author and do not necessarily represent those
of Radan Computational Ltd. The recipient(s) of this message should check it and any attached
files for viruses: Radan Computational will accept no liability for any damage caused by any
virus transmitted by this email.
Mime
View raw message