Bug#347642: [php-maint] Bug#347642: php5-5.1.1-1 segfaults
On Thu, January 12, 2006 11:02, Steve Langasek wrote: This shows two incompatible versions of libmysqlclient being loaded into memory. Whatever is causing libmysqlclient12 to be loaded is what's causing your segfault. Figure out what that is, and upgrade it to a libmysqlclient15 version. well, it's debian/unstable anyway and several other packages still depend on libmysqlclient12, so i cannot uninstall it. By all rights, however, the current version of libmysqlclient15 in Debian shouldn't be subject to such bugs due to its use of versioned symbols. (It should still be possible for libmysqlclient12 to call into libmysqlclient15, but not vice-versa.) Please confirm which version of libmysqlclient15 you have installed, as this may warrant a separate bug report. ok, i'll do that. thank you for your assistance, Christian. -- make bzImage, not war -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347642: [php-maint] Bug#347642: php5-5.1.1-1 segfaults
On Fri, Jan 13, 2006 at 08:35:41AM -, Christian Kujau wrote: On Thu, January 12, 2006 11:02, Steve Langasek wrote: This shows two incompatible versions of libmysqlclient being loaded into memory. Whatever is causing libmysqlclient12 to be loaded is what's causing your segfault. Figure out what that is, and upgrade it to a libmysqlclient15 version. well, it's debian/unstable anyway and several other packages still depend on libmysqlclient12, so i cannot uninstall it. Then tell us what packages you're using that depend on it, so we can reassign this bug there. By all rights, however, the current version of libmysqlclient15 in Debian shouldn't be subject to such bugs due to its use of versioned symbols. (It should still be possible for libmysqlclient12 to call into libmysqlclient15, but not vice-versa.) Please confirm which version of libmysqlclient15 you have installed, as this may warrant a separate bug report. ok, i'll do that. Uh? Does this mean I should expect another mail from you soon with this information? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#347642: [php-maint] Bug#347642: php5-5.1.1-1 segfaults
On Fri, January 13, 2006 09:53, Steve Langasek wrote: well, it's debian/unstable anyway and several other packages still depend on libmysqlclient12, so i cannot uninstall it. Then tell us what packages you're using that depend on it, so we can reassign this bug there. these are the packages depending on libmysqlclient12: [EMAIL PROTECTED]:~# dpkg -P libmysqlclient12 dpkg: dependency problems prevent removal of libmysqlclient12: libmailutils0 depends on libmysqlclient12. mailutils depends on libmysqlclient12. courier-authmysql depends on libmysqlclient12. libpam-mysql depends on libmysqlclient12. proftpd-mysql depends on libmysqlclient12. proftpd-mysql depends on libmysqlclient12 (= 4.0.23). proftpd-mysql depends on libmysqlclient12. proftpd-mysql depends on libmysqlclient12 (= 4.0.23). snort-mysql depends on libmysqlclient12; however: Package libmysqlclient12 is to be removed. libapache2-mod-auth-mysql depends on libmysqlclient12. libdbd-mysql depends on libmysqlclient12. libnss-mysql depends on libmysqlclient12. dpkg: error processing libmysqlclient12 (--purge): dependency problems - not removing Errors were encountered while processing: libmysqlclient12 should still be possible for libmysqlclient12 to call into libmysqlclient15, but not vice-versa.) Please confirm which version of libmysqlclient15 you have installed, as this may warrant a separate bug report. ok, i'll do that. Uh? Does this mean I should expect another mail from you soon with this information? hm, did i must've misunderstood you, because i really opened another bug for libmysqlclient15 (for calling libmysqlclient12): #347878: libmysqlclient15 calls into libmysqlclient12, leading to apache2 segfault i'm sorry, if this was the wrong thing to do. thank your for your assistance, Christian. -- make bzImage, not war -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347642: [php-maint] Bug#347642: php5-5.1.1-1 segfaults
On Fri, Jan 13, 2006 at 09:21:45AM -, Christian Kujau wrote: On Fri, January 13, 2006 09:53, Steve Langasek wrote: well, it's debian/unstable anyway and several other packages still depend on libmysqlclient12, so i cannot uninstall it. Then tell us what packages you're using that depend on it, so we can reassign this bug there. these are the packages depending on libmysqlclient12: [EMAIL PROTECTED]:~# dpkg -P libmysqlclient12 dpkg: dependency problems prevent removal of libmysqlclient12: libmailutils0 depends on libmysqlclient12. mailutils depends on libmysqlclient12. courier-authmysql depends on libmysqlclient12. libpam-mysql depends on libmysqlclient12. proftpd-mysql depends on libmysqlclient12. proftpd-mysql depends on libmysqlclient12 (= 4.0.23). proftpd-mysql depends on libmysqlclient12. proftpd-mysql depends on libmysqlclient12 (= 4.0.23). snort-mysql depends on libmysqlclient12; however: Package libmysqlclient12 is to be removed. libapache2-mod-auth-mysql depends on libmysqlclient12. libdbd-mysql depends on libmysqlclient12. libnss-mysql depends on libmysqlclient12. dpkg: error processing libmysqlclient12 (--purge): dependency problems - not removing Errors were encountered while processing: libmysqlclient12 Oh, quite a few then... we'll just have to wait for this transition to complete, in that case. should still be possible for libmysqlclient12 to call into libmysqlclient15, but not vice-versa.) Please confirm which version of libmysqlclient15 you have installed, as this may warrant a separate bug report. ok, i'll do that. Uh? Does this mean I should expect another mail from you soon with this information? hm, did i must've misunderstood you, because i really opened another bug for libmysqlclient15 (for calling libmysqlclient12): #347878: libmysqlclient15 calls into libmysqlclient12, leading to apache2 segfault i'm sorry, if this was the wrong thing to do. Well, I meant I wanted you to tell me what version of libmysqlclient15 you have installed -- but seeing that you do have a current version installed, filing a bug against libmysqlclient15 was the right thing to do, yes. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#347642: [php-maint] Bug#347642: php5-5.1.1-1 segfaults
On Thu, January 12, 2006 04:31, Adam Conrad wrote: If you can get me a GDB backtrace, that would be great: here's the bt, and it seems like libmysqlclient.so.12 is to blame? [EMAIL PROTECTED]:~# gdb apache2 GNU gdb 6.4-debian Copyright 2005 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i486-linux-gnu...(no debugging symbols found) Using host libthread_db library /lib/tls/libthread_db.so.1. (gdb) run -X Starting program: /usr/sbin/apache2 -X (no debugging symbols found) (no debugging symbols found) [.these messages repeat 20 times or so] [ now pointing the browser to the index.php] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1215121184 (LWP 6378)] 0xb79054cf in vio_in_addr () from /usr/lib/libmysqlclient.so.12 (gdb) bt #0 0xb79054cf in vio_in_addr () from /usr/lib/libmysqlclient.so.12 #1 0xb77bad4a in mysql_real_connect () from /usr/lib/libmysqlclient.so.15 #2 0xb6c9d431 in zif_mysql_field_name () from /usr/lib/php5/20051025/mysql.so #3 0xb72030be in execute () from /usr/lib/apache2/modules/libphp5.so #4 0xb72026d8 in execute () from /usr/lib/apache2/modules/libphp5.so #5 0xb7202b79 in execute () from /usr/lib/apache2/modules/libphp5.so #6 0xb72026d8 in execute () from /usr/lib/apache2/modules/libphp5.so #7 0xb7202b79 in execute () from /usr/lib/apache2/modules/libphp5.so #8 0xb72026d8 in execute () from /usr/lib/apache2/modules/libphp5.so #9 0xb7202b79 in execute () from /usr/lib/apache2/modules/libphp5.so #10 0xb72026d8 in execute () from /usr/lib/apache2/modules/libphp5.so #11 0xb72089bf in zend_get_zval_ptr () from /usr/lib/apache2/modules/libphp5.so #12 0xb72026d8 in execute () from /usr/lib/apache2/modules/libphp5.so #13 0xb71da17e in zend_execute_scripts () from /usr/lib/apache2/modules/libphp5.so #14 0xb7199a8e in php_execute_script () from /usr/lib/apache2/modules/libphp5.so #15 0xb7278ea8 in zend_get_zval_ptr () from /usr/lib/apache2/modules/libphp5.so #16 0x08077336 in ap_run_handler () #17 0x08077732 in ap_invoke_handler () #18 0x080696fd in ap_process_request () #19 0x08064b19 in _start () (gdb) -- make bzImage, not war -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347642: [php-maint] Bug#347642: php5-5.1.1-1 segfaults
On Thu, Jan 12, 2006 at 09:22:40AM -, Christian Kujau wrote: On Thu, January 12, 2006 04:31, Adam Conrad wrote: If you can get me a GDB backtrace, that would be great: here's the bt, and it seems like libmysqlclient.so.12 is to blame? Yes. More specifically, the fact that you have some apache module installed that *uses* libmysqlclient12 is to blame. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1215121184 (LWP 6378)] 0xb79054cf in vio_in_addr () from /usr/lib/libmysqlclient.so.12 (gdb) bt #0 0xb79054cf in vio_in_addr () from /usr/lib/libmysqlclient.so.12 #1 0xb77bad4a in mysql_real_connect () from /usr/lib/libmysqlclient.so.15 This shows two incompatible versions of libmysqlclient being loaded into memory. Whatever is causing libmysqlclient12 to be loaded is what's causing your segfault. Figure out what that is, and upgrade it to a libmysqlclient15 version. By all rights, however, the current version of libmysqlclient15 in Debian shouldn't be subject to such bugs due to its use of versioned symbols. (It should still be possible for libmysqlclient12 to call into libmysqlclient15, but not vice-versa.) Please confirm which version of libmysqlclient15 you have installed, as this may warrant a separate bug report. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#347642: [php-maint] Bug#347642: php5-5.1.1-1 segfaults
Christian Kujau wrote: when updating to php5.1.1-1 one of the application i used made apache2-mpm-prefork segfault: If you can get me a GDB backtrace, that would be great: # apt-get install gdb # gdb apache2 (gdb) run -X [ hit the index with a web browser, and wait for gdb to tell you it's segfaulted ] (gdb) bt [copy and paste the output after you asked for a backtrace and send that back to the bug ] ... Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
