Bug #66854 --debug in mysqlimport does not work
Submitted: 18 Sep 2012 9:49 Modified: 16 May 2014 2:20
Reporter: Zhihong He Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S4 (Feature request)
Version:before 5.5.25a OS:Linux
Assigned to: CPU Architecture:Any

[18 Sep 2012 9:49] Zhihong He 
Description:
May I know whether --debug='filename.log' works? I have tried, but there is no .log file generated. As I searched a lot in the internet, all the answers(from 2004-2012) turn out that this function dose not work. Just want to confirm here in the official website. If this function dose not work, then why this option is still there? 

Thanks~

How to repeat:
when using mysqlimport with --debug='filename.log', no .log file created

Suggested fix:
move it or fix it
[2 Feb 2013 12:07] MySQL Verification Team 
You are correct, it just doesn't work.

in mysqlimport.cc we have:

  {"debug",'#', "Output debug log. Often this is 'd:t:o,filename'.", 0, 0, 0,
   GET_STR, OPT_ARG, 0, 0, 0, 0, 0, 0},

in other utils, like mysql.cc we have:

#ifdef DBUG_OFF
  {"debug", '#', "This is a non-debug version. Catch this and exit.",
   0,0, 0, GET_DISABLED, OPT_ARG, 0, 0, 0, 0, 0, 0},
#else
  {"debug", '#', "Output debug log.", &default_dbug_option,
   &default_dbug_option, 0, GET_STR, OPT_ARG, 0, 0, 0, 0, 0, 0},
#endif
[16 May 2014 2:20] Paul DuBois 
Noted in 5.7.5 changelog.

For non-debug builds of several client programs, the --help message
did not correctly indicate that the --debug, --debug-check, and
--debug-info apply only for debug builds.