I hate to say it, but drop back to 3.0 and test on RH 7.2. If it breaks, then there's something different in the combo between AOLserver and RedHat 7.2.
If it works, then upgrade to AOLserver 3.1 and test, then 3.2 and test etc. until you get to 3.4.2, also on RedHat 7.2. Let's find out which upgrade breaks it. When it breaks, get a backtrace with GDB, then look at the sources where it breaks and see what's changed between the code that broke and the version before it. Frankly, I'm surprised that a bad path would cause a segfault, which leads me to believe that some var or pointer isn't being initialized before use. /s. > Scott, > > I've been using this Aolserver 3.0 + PHP 4.0.6 for over a year with no > problem -- this is new (mis)behavior. In what I'm trying to setup now, the > PHP version is the same, but I'm trying to use new versions of Aolserver > (3.4.2) and RedHat (7.2, old server has 6.2). I cannot think of any way > that Aolserver is causing this problem for PHP, though. > > At 06:59 PM 11/26/2001 -0600, you wrote: > >Hi Sean, > > > >Is this something you can fix on your own? It's possible that the PHP module > >for AOLserver is doing this (i.e. it's building a path without checking for > >relative paths); I'm not sure as I've never used the module or PHP. > > > >/s. > > Sean Redmond > Brooklyn Museum of Art > > > > >
