| Bug #44900 | valgrind warning in log_slow_statement | ||
|---|---|---|---|
| Submitted: | 15 May 2009 10:48 | Modified: | 4 Sep 2012 11:24 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Logging | Severity: | S3 (Non-critical) |
| Version: | 5.1.35 | OS: | Linux (32-bit fc8) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | slow query log, valgrind | ||
[28 Dec 2009 21:55]
Sveta Smirnova
Thank you for the report. I can not repeat described behavior. Which server options do you use? Which query did you issue?
[29 Jan 2010 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".
Description: Got this valgrind warning from 5.1.35: Thread 13: Conditional jump or move depends on uninitialised value(s) at: log_slow_statement(THD*) (sql_parse.cc:1630) by: dispatch_command(enum_server_command, THD*, char*, unsigned(sql_parse.cc:1593) by: do_command(THD*) (sql_parse.cc:857) by: handle_one_connection (sql_connect.cc:1115) by: start_thread (in /lib/libpthread-2.5.so) by: clone (in /lib/libc-2.5.so) How to repeat: read the code, or run any long query. i didn't have slow query log enabled. line 1630 of sql_parse.cc is this: if (((end_utime_of_query - thd->utime_after_lock) > thd->variables.long_query_time || ((thd->server_status & (SERVER_QUERY_NO_INDEX_USED | SERVER_QUERY_NO_GOOD_INDEX_USED)) && opt_log_queries_not_using_indexes && !(sql_command_flags[thd->lex->sql_command] & CF_STATUS_COMMAND))) && thd->examined_row_count >= thd->variables.min_examined_row_limit) I don't know which variable is to blame..