This is going to be long. It's also incomplete because I want to run one more
test that came to me this AM.
--
Output of perl -v:
This is perl, version 5.005_02 built for PA-RISC2.0
Copyright 1987-1998, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
G
> What I find odd is that all of the sudden people seem to be coming out of
> the woodwork about this stuff. Whe I searched through mailing list
> archives, some of them going back years, I found something odd... Many
> people were talking about this same problem between December of last year
> [Tue Dec 14 15:44:22 1999] [notice] child pid 13243 exit signal
> Segmentation fault (11)
> --
...
> If someone could please point me in the right direction or FAQ, I, and my
> sanity, would be most happy.
there are quite a few tips on debugging core dumps posted between last
nig
The reason I don't think it has anything to do with DBD is that, as I said,
I have been able to use a script which calls DBD::Oracle not running under
mod_perl and everything works great. This is on the same box that dies when
calling DBD through mod_perl. And again, the same script, when run
Jason Simms wrote:
> I am having a problem similar to yours... Whenever I try an connect to
> Oracle (using DBD and DBI), I am getting a segmentation fault / child pid
> exit error. But this only happens under mod_perl, and only on one box in
> particular. If I move the exact same script to an
I am having a problem similar to yours... Whenever I try an connect to
Oracle (using DBD and DBI), I am getting a segmentation fault / child pid
exit error. But this only happens under mod_perl, and only on one box in
particular. If I move the exact same script to another box, everything
wo
Before I go too far into troubleshooting this, I am working on a module
that involves parsing a requested html document. When I run it by
accessing a page I get a 500 Server error and in my error log I get the
following (I have 'use diagnostics' activated):
Use of uninitialized
