Bug #13697 | mysql-max immediate crash on ev6, signal 11 and segfaults. (ds20e) | ||
---|---|---|---|
Submitted: | 3 Oct 2005 6:53 | Modified: | 3 Nov 2005 8:16 |
Reporter: | Beracah Yankama | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | mysql-max-5.0.10 alphaev6 | OS: | Linux (CentOS 4.1 (RedHat FC3) AlphaAXP) |
Assigned to: | CPU Architecture: | Any |
[3 Oct 2005 6:53]
Beracah Yankama
[3 Oct 2005 6:59]
Beracah Yankama
oh, I wanted to add that gnu compilation of the same source, while it runs, yields kernel unaligned traps, so the CCC -fast option, or CCC might be turning into an error in the binary. also in mysqladmin: mysqladmin(2799): unaligned trap at 000002000005a038: 0000000120017d69 28 1 Oct 3 02:16:06 alpha_leonis kernel: mysqladmin(2799): unaligned trap at 000002000005a048: 0000000120017d69 2c 2 Oct 3 02:16:06 alpha_leonis kernel: mysqladmin(2799): unaligned trap at 000002000005a038: 0000000120017d69 28 1 Oct 3 02:16:06 alpha_leonis kernel: mysqladmin(2799): unaligned trap at 000002000005a048: 0000000120017d69 2c 2
[3 Oct 2005 7:08]
Beracah Yankama
Actually, it also occurs in the mysql-max 4.1 alpha ev6 binary. Maybe it is bcs (my) FC3 uses glibc2.3, and this is build for glibc2.1 -- I thought the ev6 binary was built statically...
[3 Oct 2005 8:16]
Valeriy Kravchuk
Please, try to build from 5.0.13-rc sources available at http://dev.mysql.com/downloads/mysql/5.0.html. 5.0.10 is a bit old, really. I was not able to found our certified binaries for your platform. Moreover, we have only one Linux -alphaev6 machine, with SuSE, not CentOS nor FC3, so I will not be able to reproduce your problem exactly in any case. Inform me about the results of your build attempt. Please, include the configure options used in case of any failures during build.
[4 Nov 2005 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".