Re: DBI make apache fail in perl58.dll
Can you retrieve a backtrace from the core file? The version that I was using before 1.30 (I think it was 1.29) was blowing so badly that it was leaving no stack. this is the only uninformative stack i have, having no debug version. I am trying to build one... PERL58! 280681d9() -- error here access violation DBI! 003970b6() PERL58! 2803f289() PERL58! 2805cf4c() PERL58! 2806b821() PERL58! 2808596f() MOD_PERL! 100018b7() LIBHTTPD! 6ff012a6() pascal
Re: DBI make apache fail in perl58.dll
PERL58! 280681d9() -- error here access violation DBI! 003970b6() PERL58! 2803f289() PERL58! 2805cf4c() PERL58! 2806b821() PERL58! 2808596f() MOD_PERL! 100018b7() LIBHTTPD! 6ff012a6() Hi here is maybe more informative stack trace WARNING: Stack unwind information not available. Following frames may be wrong. perl58!Perl_ptr_table_fetch+0x8 DBI+0x70b6 perl58!Perl_sv_compile_2op+0x76ca perl58!Perl_runops_standard+0xc perl58!perl_clone_using+0x1eac perl58!perl_clone_host+0x6d mod_perl!modperl_interp_new+0x39 libhttpd!ap_run_post_config+0x36 pascal
Re: DBI make apache fail in perl58.dll
pascal barbedor wrote: PERL58! 280681d9() -- error here access violation DBI! 003970b6() PERL58! 2803f289() PERL58! 2805cf4c() PERL58! 2806b821() PERL58! 2808596f() MOD_PERL! 100018b7() LIBHTTPD! 6ff012a6() Hi here is maybe more informative stack trace WARNING: Stack unwind information not available. Following frames may be wrong. perl58!Perl_ptr_table_fetch+0x8 DBI+0x70b6 perl58!Perl_sv_compile_2op+0x76ca perl58!Perl_runops_standard+0xc perl58!perl_clone_using+0x1eac perl58!perl_clone_host+0x6d mod_perl!modperl_interp_new+0x39 libhttpd!ap_run_post_config+0x36 that's a weird trace. it's still incomplete, but getting better. One things missing is 'DBI+0x70b6'. Can you now rebuild DBI? It should pick the debug flags from perl (which you've apparently just rebuilt). __ Stas BekmanJAm_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
Re: DBI make apache fail in perl58.dll
SharedUserData!SystemCallStub+0x4 ntdll!ZwTerminateProcess+0xc kernel32!_ExitProcess+0x57 kernel32!ExitProcess+0x11 msvcrt!__crtExitProcess+0x2f msvcrt!_cinit+0xe4 msvcrt!exit+0xe WARNING: Stack unwind information not available. Following frames may be wrong. perl58!Perl_Tregnarrate_ptr+0x14809d perl58!Perl_Tregnarrate_ptr+0x57255 perl58!Perl_Tregnarrate_ptr+0x56ef8 perl58!Perl_Tregnarrate_ptr+0x13fc84 perl58!Perl_Tregnarrate_ptr+0x13fcd9 perl58!Perl_Tregnarrate_ptr+0xfeb7a perl58!Perl_Tregnarrate_ptr+0xfe465 DBI!XS_DBI__clone_dbis+0x27b DBI!XS_DBI__clone_dbis+0x100 perl58!Perl_Tregnarrate_ptr+0x96df8 perl58!Perl_Tregnarrate_ptr+0x17de8 perl58!Perl_Tregnarrate_ptr+0x52c21 perl58!Perl_Tregnarrate_ptr+0x5237c I am affraid it's the best I can do, it's very hard to compile debug on win32 I have seemingly compiled perl58 DEBUG (there was a complain about missing vc60.pdb, and I supplied one I found ) I cannot compile debug either modperl1-99_04 either _05 against my debug perl. so I just copied from perl/site/lib everything concerning modperl into the perldebug site/lib tree (don't know if this is liable) I also properly installed DBI-1.30 in the perldebug site/lib tree then I ran apache in windbg and got this stacktrace also here is the last loading modules sequence inside apache ModLoad: 6fbf 6fbf6000 C:\Apache2\modules\mod_userdir.so ModLoad: 2800 281a3000 C:\perld\bin\perl58.dll ModLoad: 1000 1001 C:\Apache2\modules\mod_perl.so ModLoad: 71a9 71a98000 C:\WINDOWS\System32\wshtcpip.dll ModLoad: 0036 00383000 C:\perld\site\lib\auto\DBI\DBI.dll ModLoad: 0039 00399000 C:\perld\site\lib\auto\Apache\RequestRec\RequestRec.dll ModLoad: 003a 003a6000 C:\perld\site\lib\auto\Apache\RequestIO\RequestIO.dll ModLoad: 003b 003b8000 C:\perld\site\lib\auto\ModPerl\Const\Const.dll ModLoad: 003c 003c5000 C:\perld\site\lib\auto\Apache\Const\Const.dll --error at this point since it is past DBI.dll , maybe this is because I copied incompatible modperl to perld site/lib tree. hope this can help pascal
[modperl-2.0] unresolved external on win32 when compiling
Hi when compiling modperl 1.99_05 (from today cvs) with MP_DEBUG=1 there is un unresolved external RequestIO.obj : unresolved external symbol _times RequestIO.dll fatal LNK error this is with perl 5.8.0 compiled with DEBUG flag win XP MSVC6 best regards pascal PS modperl-1.99_04 downloaded from perl.apache.org shows this error (with same compiling configuration) mod_perl.c(519) : error ap_register_output_filter different types formal and actual parameters 3 mod_perl.c (523): error ap_register_input_filter too fewactual parameters
Re: [modperl-2.0] unresolved external on win32 when compiling
pascal barbedor wrote: Hi when compiling modperl 1.99_05 (from today cvs) with MP_DEBUG=1 there is un unresolved external RequestIO.obj : unresolved external symbol _times RequestIO.dll fatal LNK error this is with perl 5.8.0 compiled with DEBUG flag win XP MSVC6 Perhaps someone on win32 can check this out. Randy? PS modperl-1.99_04 downloaded from perl.apache.org shows this error (with same compiling configuration) mod_perl.c(519) : error ap_register_output_filter different types formal and actual parameters 3 mod_perl.c (523): error ap_register_input_filter too few actual parameters that's ok. you aren't supposed to build _04 with apache 2.0.40 or higher. it's time to release _05. __ Stas BekmanJAm_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
Re: DBI make apache fail in perl58.dll
pascal barbedor wrote: SharedUserData!SystemCallStub+0x4 ntdll!ZwTerminateProcess+0xc kernel32!_ExitProcess+0x57 kernel32!ExitProcess+0x11 msvcrt!__crtExitProcess+0x2f msvcrt!_cinit+0xe4 msvcrt!exit+0xe WARNING: Stack unwind information not available. Following frames may be wrong. perl58!Perl_Tregnarrate_ptr+0x14809d perl58!Perl_Tregnarrate_ptr+0x57255 perl58!Perl_Tregnarrate_ptr+0x56ef8 perl58!Perl_Tregnarrate_ptr+0x13fc84 perl58!Perl_Tregnarrate_ptr+0x13fcd9 perl58!Perl_Tregnarrate_ptr+0xfeb7a perl58!Perl_Tregnarrate_ptr+0xfe465 DBI!XS_DBI__clone_dbis+0x27b DBI!XS_DBI__clone_dbis+0x100 perl58!Perl_Tregnarrate_ptr+0x96df8 perl58!Perl_Tregnarrate_ptr+0x17de8 perl58!Perl_Tregnarrate_ptr+0x52c21 perl58!Perl_Tregnarrate_ptr+0x5237c I am affraid it's the best I can do, it's very hard to compile debug on win32 I have seemingly compiled perl58 DEBUG (there was a complain about missing vc60.pdb, and I supplied one I found ) I cannot compile debug either modperl1-99_04 either _05 against my debug perl. so I just copied from perl/site/lib everything concerning modperl into the perldebug site/lib tree (don't know if this is liable) I also properly installed DBI-1.30 in the perldebug site/lib tree then I ran apache in windbg and got this stacktrace also here is the last loading modules sequence inside apache ModLoad: 6fbf 6fbf6000 C:\Apache2\modules\mod_userdir.so ModLoad: 2800 281a3000 C:\perld\bin\perl58.dll ModLoad: 1000 1001 C:\Apache2\modules\mod_perl.so ModLoad: 71a9 71a98000 C:\WINDOWS\System32\wshtcpip.dll ModLoad: 0036 00383000 C:\perld\site\lib\auto\DBI\DBI.dll ModLoad: 0039 00399000 C:\perld\site\lib\auto\Apache\RequestRec\RequestRec.dll ModLoad: 003a 003a6000 C:\perld\site\lib\auto\Apache\RequestIO\RequestIO.dll ModLoad: 003b 003b8000 C:\perld\site\lib\auto\ModPerl\Const\Const.dll ModLoad: 003c 003c5000 C:\perld\site\lib\auto\Apache\Const\Const.dll --error at this point since it is past DBI.dll , maybe this is because I copied incompatible modperl to perld site/lib tree. hope this can help I don't think this has anything to do with loading dlls. It definitely happens when DBI gets loaded. May be DBI-1.30 still needs work, as it seems to work on linux, but not on windows. Have you considered asking on the dbi-users list? including posting the traces there? __ Stas BekmanJAm_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
Re: [modperl-2.0] unresolved external on win32 when compiling
Hi when compiling modperl 1.99_05 (from today cvs) with MP_DEBUG=1 first error : modperl_xsinit.lo : fatal error : incompatible pdb format in c:\modperl-2.0\src\modules\perl\vc60.pdb ; delete and rebuild I don't know what the delete and rebuild means. after I delete the vc60.pdb file mentionned above, and retype nmake compilation continues without debugging information and hangs on this second error i mentioned before : there is un unresolved external RequestIO.obj : unresolved external symbol _times RequestIO.dll fatal LNK error this is with perl 5.8.0 compiled with DEBUG flag win XP MSVC6 Apache 2.0.40 pascal
Re: [modperl-2.0] unresolved external on win32 when compiling
On Sun, 18 Aug 2002, Stas Bekman wrote: pascal barbedor wrote: Hi when compiling modperl 1.99_05 (from today cvs) with MP_DEBUG=1 there is un unresolved external RequestIO.obj : unresolved external symbol _times RequestIO.dll fatal LNK error this is with perl 5.8.0 compiled with DEBUG flag win XP MSVC6 Perhaps someone on win32 can check this out. Randy? I get the missing _times error too - I think this is related to the use of times() in MP_START_TIMES() and MP_END_TIMES() in src/modules/perl/modperl_time.h. I looked on some VC++ newsgroups - there were questions about a VC++ equivalent of times(), but no real answers. -- best regards, randy
Mod_perl Application Development
I'm curious to know how people approach application development with mod_perl in situations where there could be dozens of distinct screens/interfaces. I'm currently using the HTML::Template system. Here's a few approaches I thought of: 1. Single monolithic content handler. Could be hard to maintain. 2. Distinct content handlers each with their own Location directive. Could be a pain to maintain the server config. 3. Take a small performance hit and use an Apache::Registry script for each screen to handle the content phase. Use 'PerlSetupEnv Off', $r and Apache:: modules and don't bother being backwardly compatible with CGI. Thanks, Jonathan
