| Bug #56837 | binlog crash tests should not generate core files | ||
|---|---|---|---|
| Submitted: | 17 Sep 2010 9:24 | Modified: | 17 Sep 2010 11:40 |
| Reporter: | Tor Didriksen | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
| Version: | next-mr | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[17 Sep 2010 11:40]
Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. Duplicate of bug #52172
Description: binlog crash tests will kill the server to test crash behaviour. These crashes generate un-necessary core files. The coredumps are generated by lines like DBUG_EXECUTE_IF("crash_purge_before_update_index", DBUG_ABORT();); I think that _exit(EXIT_FAILURE) , possibly wrapped in a function/macro, would be more appropriate. How to repeat: ./mtr --debug binlog.binlog_index Suggested fix: Use _exit(EXIT_FAILURE) rather than abort() when killing server.