Walter Stingl wrote:
> Hi,
>
> i installed Apache/2.0.40 (Win32) mod_perl/1.99_05-dev Perl/v5.6.1 on a
> Windows NT (Servicepack 6a)-System.
>
> When i try to run a CGI-Script "abfert1.pl" with ModPerl::Registry the
> browser hangs forever displaying a blank window.
> There is no Error-Entry
Hi,
i installed Apache/2.0.40 (Win32)
mod_perl/1.99_05-dev Perl/v5.6.1 on a Windows NT (Servicepack 6a)-System.
When i try to run a CGI-Script "abfert1.pl" with
ModPerl::Registry the browser hangs forever displaying a blank window.
There is no Error-Entry in the Apache Error Log .
Th
Rich Duzenbury wrote:
> Hello list,
>
> Does anyone have a working link to a pdf version (mod_perl 1.27) of the
> guide? Found one in the archives that no longer works...
sorry, I was working around the problems on apache.org and changing the
auto-build script and the pdf build was broken. It
Hello list,
Does anyone have a working link to a pdf version (mod_perl 1.27) of the
guide? Found one in the archives that no longer works...
I tried cvs'ing the data and doing the build deal referenced on
perl.apache.org, but I'm missing something as I get an error from
DocSet/Util.pm. It's
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 main
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
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 menti
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
> wron
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
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 d
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
p
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
> >
> > 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 infor
pascal barbedor wrote:
>>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
>
> 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() <-- e
15 matches
Mail list logo