[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

2012-03-12 Thread JC Hulce
Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu you're reporting this issue on is in End of Life status, and newer versions have fixed this issue. You can learn more about this at https://wiki.ubuntu.com/Releases ** Changed in:

[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

2009-08-26 Thread Shang Wu
Seems to be directly related to: http://bugs.mysql.com/bug.php?id=21476 ** Bug watch added: MySQL Bug System #21476 http://bugs.mysql.com/bug.php?id=21476 -- MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...) https://bugs.launchpad.net/bugs/394036 You received this bug notification

[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

2009-08-24 Thread Mathias Gug
On a related note, here is a link where previous versions of mysql 5.0 can be downloaded: http://snaps.mysql.com/archives.php?p=mysql-5.0o=other -- MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...) https://bugs.launchpad.net/bugs/394036 You received this bug notification because you are

[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

2009-08-23 Thread Andreas Olsson
I can reproduce this bug in MySQL 5.0.24a-9ubuntu2.4 (edgy) It appears to have been fixed in MySQL 5.0.38-0ubuntu1 (feisty) Do note that even affected MySQL versions can detect/handle ERROR 1436. It seems as if the option thread_stack has to be within a certain range for this bug to manifest

[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

2009-08-20 Thread Mathias Gug
What needs to be to move things forward on dapper is to figure out which version of mysql has the fix. 1. Narrow down the range of versions to test by testing mysql packages from every release (edgy, feisty, gutsy). 2. Figure out if mysql keeps an archive of all previous releases. If not, look

[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

2009-07-08 Thread Mathias Gug
On hardy and above the server doesn't crash. Instead the following error is reported: ERROR 1436 (HY000): Thread stack overrun: 250312 bytes used of a 262144 byte stack, and 12000 bytes needed. Use 'mysqld -O thread_stack=#' to specify a bigger stack. Marking bug Fixed Released for hardy and

[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

2009-07-01 Thread Daniel van Eeden
I saw a similair query which seem to crash the MySQL client (version 5.0.22-0ubuntu6.06.11). mysql SELECT CONCAT('',

[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

2009-07-01 Thread Daniel van Eeden
The above query together with this config crashes the server. # egrep -v ^($|#) /etc/mysql/my.cnf [client] port= 3306 socket = /var/run/mysqld/mysqld.sock [mysqld_safe] socket = /var/run/mysqld/mysqld.sock nice= 0 core-file-size = unlimited [mysqld]