Bug #4031 | 4.1.2 x86 icc binaries seem to have a problem related to net_buffer_length | ||
---|---|---|---|
Submitted: | 7 Jun 2004 4:41 | Modified: | 25 Sep 2004 7:37 |
Reporter: | Matthew Lord | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Compiling | Severity: | S2 (Serious) |
Version: | 4.1.2-standard-alpha-pc-linux-i686-icc | OS: | Linux (linux) |
Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[7 Jun 2004 4:41]
Matthew Lord
[26 Aug 2004 8:19]
Ramil Kalimullin
Hi Matthew, Just tried to repeat that using mysql-standard-4.1.3-beta-pc-linux-i686-icc on Red Hat 8.0 (2.4.18-14) - no luck, everything works fine. What exact net_buffer_length value did you use? Could you try mysql-standard-4.1.3-beta-pc-linux-i686-icc on your box? Regards, Ramil.
[31 Aug 2004 9:45]
Ramil Kalimullin
Thank you for taking the time to report a problem. Unfortunately you are not using a current version of the product your reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/ If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of MySQL.
[1 Sep 2004 4:38]
Matthew Lord
Hi Ramil, Did you actually test this with 4.1.3? I doubt that this has been fixed as it was icc specific and related to static libc problems that also incur the problems regarding resolveip and switching users. Best Regards
[1 Sep 2004 10:43]
Ramil Kalimullin
Hi Matthew, Yes, I did. As I wrote, I downloaded 4.1.3 icc build and installed it without any problems on Red Hat 8.0 box. Best regards. P.S. Just tried to repeat the issue once again - no luck :(
[25 Sep 2004 7:37]
Ramil Kalimullin
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/ Additional info: Probably it was a build problem. I'm closing the bug as 4.1.4 works properly.