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: 6fbf0000 6fbf6000 C:\Apache2\modules\mod_userdir.so > ModLoad: 28000000 281a3000 C:\perld\bin\perl58.dll > ModLoad: 10000000 10010000 C:\Apache2\modules\mod_perl.so > ModLoad: 71a90000 71a98000 C:\WINDOWS\System32\wshtcpip.dll > ModLoad: 00360000 00383000 C:\perld\site\lib\auto\DBI\DBI.dll > ModLoad: 00390000 00399000 > C:\perld\site\lib\auto\Apache\RequestRec\RequestRec.dll > ModLoad: 003a0000 003a6000 > C:\perld\site\lib\auto\Apache\RequestIO\RequestIO.dll > ModLoad: 003b0000 003b8000 C:\perld\site\lib\auto\ModPerl\Const\Const.dll > ModLoad: 003c0000 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 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
