gt;
> Drew
>
> At 07:59 PM 7/28/2002 -0700, Greg Rumple wrote:
> >Yup, this is it. If I build it without DSO support, it appears to work.
> >Of course I build this with mod_php, mod_ssl, mod_perl, and a couple of
> >custom modules. So running without DSO support isn&#x
88f in Perl_sv_free () from /usr/lib/libperl.so.5.6
> > #4 0x40274d6f in Perl_sv_vcatpvfn () from /usr/lib/libperl.so.5.6
> > #5 0x4026a378 in Perl_sv_add_arena () from /usr/lib/libperl.so.5.6
> > #6 0x4026a434 in Perl_sv_clean_all () from /usr/lib/libperl.so.5.6
> > #7 0x40219b75 in perl_destruct () from /usr/lib/libperl.so.5.6
> > #8 0x401bbb77 in perl_shutdown (s=0x0, p=0x0) at mod_perl.c:294
> > #9 0x401bc507 in mp_dso_unload (data=0x8094bdc) at mod_perl.c:489
> > #10 0x08050c39 in run_cleanups (c=0x80a06cc) at alloc.c:1713
> > #11 0x0804f2d5 in ap_clear_pool (a=0x8094bdc) at alloc.c:538
> > #12 0x08060bfc in standalone_main (argc=6, argv=0xbac4) at
> http_main.c:5058
> > #13 0x080615cc in main (argc=6, argv=0xbac4) at http_main.c:5448
> >
> > The test.pl script works fine by it's self. Turning on full PERL
> > debugging/tracing yields that the actual script has fully finished, and
> > that it's in the tear down of the actualy perl stuff that this failure
> > is coming from. Not from the script per se. But it is the script that
> > is causing this problem. Commenting out the connect and disconnect
> > lines causes the server to startup and function just fine.
> >
> > So I'm not quite sure what to do. I know I can get my entire system
> > working if I don't make the calls to Informix at startup (it appears
> > it's purely the connect that causes the error (whether it's a good
> > connect or not, I tried giving it a bogus password, and it still
> > crashes)), but well that's kind of a pain in the butt.
> >
> > So if anyone has ANY clues, it would be sincerely appreciated, as I need
> > sleep, and I also would love to get this working.
> >
> > Thanks a ton in advance.
> >
> > Greg
> >
> >
> > --
> > Greg Rumple
> > [EMAIL PROTECTED]
>
--
Greg Rumple
[EMAIL PROTECTED]
> $dbh->disconnect();
>
> um, okay but why disconnect at all, if you know the segfault is caused by
> the connect and/or disconnect calls? have you tries simply *not*
> disconnecting? one of The Features/Advantages of Apache::DBI (over plain
> ole DBI) is that disconnect calls simlpy destroy the connection *object*
> (the perl data structure) without actually disconnecting from the DB, and
> therby maintaining a pool of cached connections, and therby speeding things
> up nicely.
I have removed the disconnect, but it makes no difference as suspected.
I will note that once the server is started, it has 0 problems
communicating with Informix, it's only in this startup script that it
blows up badly.
--
Greg Rumple
[EMAIL PROTECTED]
e.
So I'm not quite sure what to do. I know I can get my entire system
working if I don't make the calls to Informix at startup (it appears
it's purely the connect that causes the error (whether it's a good
connect or not, I tried giving it a bogus password, and it still
crashes)), but well that's kind of a pain in the butt.
So if anyone has ANY clues, it would be sincerely appreciated, as I need
sleep, and I also would love to get this working.
Thanks a ton in advance.
Greg
--
Greg Rumple
[EMAIL PROTECTED]
