Re: Finally a core bt!

3.0.5 runs fine. This script is primarily for displaying; it does two commits, both after a free_result. FWIW there are open un-freed Solid queries at the time I do the commit. I suppost I could have some kind of PHP code level bug that triggers this; this script is about 6 months old and is heavily used, so I was not looking for that. I have two versions of the Solid libs here (yes, I'm sure the libs and Solid daemon version are coordinated). I'll test with both again, but I think I've done so and it happens with both. Thanks for the quick followup; I've wanted to get 3.0.6 running for some time to start using XML. -- Michael On Wed, 20 Jan 1999, Andreas Karajannis wrote: > The coredump happens in SQLTransact, which is in the solid client > libs. SQLTransact gets called on freeing a statement only for > Solid and was introduced due to some Solid specific behaviour. > > So in short: To me, it seems to be a bug in the Solid libraries. > > Did you perform a rollback or commit in your script before calling > odbc_free_result()? > Maybe Solid doesn't like doing things twice ;-) > > -Andreas -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net