Possible Sybase Bug

I'd like to stop using sybase entirely, but that's a discussion for another day, here's the actual issue I'm having. An old site we've had for a while stopped working today after we upgraded to PHP 4.0.4PL1. We have a .shtml page doing a virtual include on two php pages (banner rotations, etc). The php pages work fine if they are called by themselves, but when included in an SSI manner, they cause a segfault. In order to track this down, I looked at the php files we were incluing through SSI. Turns out that the error went away when I changed sybase_connect to sybase_pconnect. So here's the complete list. Apache segfaults (page contains no data) when sybase_connect is called in a php page included through SSI, but sybase_pconnect works just fine. I know this because I used die() before and after the sybase_connect, and the segfault *only* occured when I tried to die after making the sybase connection. This brings me to believe there is a bug somewhere in the sybase_connect code. Fixed in the recent cvb? Ideas? -- +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Shaun M. Thomas INN Database Programmer | | Phone: (309) 743-0812 Fax : (309) 743-0830 | | Email: sthomas@townnews.com AIM : trifthen | | Web : hamster.lee.net | | | | "Most of our lives are about proving something, either to | | "ourselves or to someone else." | | -- Anonymous | +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+