• unknown's avatar
    Set --debug-check if one uses DBUG_PUSH in all clients · f9ea4275
    unknown authored
    Fixed bug in query cache that made it impossible to run mysqld with --debug
    Fixed memory leaks in mysqldump and mysqltest
    Memory leaks associated with wrong usage of mysqltest is not fixed. To find these, run
    mysql-test-run --debug mysqltest
    
    
    client/mysql_upgrade.c:
      Set --debug-check if one uses DBUG_PUSH
    client/mysqlcheck.c:
      Set --debug-check if one uses DBUG_PUSH
    client/mysqldump.c:
      Set --debug-check if one uses DBUG_PUSH
      Fixed several memory leaks
    client/mysqlimport.c:
      Set --debug-check if one uses DBUG_PUSH
    client/mysqlshow.c:
      Set --debug-check if one uses DBUG_PUSH
    client/mysqlslap.c:
      Set --debug-check if one uses DBUG_PUSH
    client/mysqltest.c:
      Set --debug-check if one uses DBUG_PUSH
      Fixed some memory leaks
      Removed MY_CHECK_ERROR argument to my_end() as mysqltest.test otherwise shows MANY memory leaks
    dbug/dbug.c:
      Fixed compiler warning
      Force flush of out_file on end
      Removed some wrong dbug_flush(0) commands that could cause crashes
    mysys/my_init.c:
      Don't write memory usage if MY_GIVE_INFO is not given
    sql/sql_cache.cc:
      Fixed bug in query cache that made it impossible to run mysqld with --debug
    f9ea4275
sql_cache.cc 137 KB