Bug #33677 | mysql-proxy core dump | ||
---|---|---|---|
Submitted: | 3 Jan 2008 21:43 | Modified: | 8 Jan 2008 10:35 |
Reporter: | Raoul Bhatia | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Proxy | Severity: | S3 (Non-critical) |
Version: | 0.6.0 | OS: | Linux (debian 4.0, kernel 2.6.21.1 i686) |
Assigned to: | Kay Roepke | CPU Architecture: | Any |
Tags: | core, mysql proxy |
[3 Jan 2008 21:43]
Raoul Bhatia
[3 Jan 2008 21:44]
Raoul Bhatia
it did not crash instantly but after running. but i dont know if it happened during a mysql-proxy restart or a regular query, ...
[3 Jan 2008 21:46]
Raoul Bhatia
core dump
Virus scan engine found a threat. This file might be infected. Attachment: core (application/octet-stream, text), 348.00 KiB.
[8 Jan 2008 10:35]
Kay Roepke
Thank you for your bug report. We believe this issue has been fixed in our source repository and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source tree is available at http://forge.mysql.com/wiki/MySQL_Proxy_Compiling The next release should be out soon.