Bug #50657 | my_getopt barfs on --loose-foo if it knows --foo-bar and --foo-baz but not --foo | ||
---|---|---|---|
Submitted: | 27 Jan 2010 11:49 | Modified: | 29 Jan 2010 21:55 |
Reporter: | Bjørn Munch | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.1+ | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | my_getopt |
[27 Jan 2010 11:49]
Bjørn Munch
[28 Jan 2010 8:04]
Sveta Smirnova
Thank you for the report. Verified as described.
[28 Jan 2010 8:04]
Sveta Smirnova
But why did you set category to libmysqld?
[2 Feb 2011 8:40]
Kristofer Pettersson
I've just tested 5.5.10-log "./mtr --mysqld=--loose-debug=asdasd alias" and this worked fine. Running "./mtr --debug=asdasd" didn't work at all. Running "./mtr --mysqld=--loose-debug" worked also. Running "./mtr --mysqld=--debug binlog.binlog_incident" gives me: binlog.binlog_incident [ skipped ] Test needs debug binaries Are you sure you are running a non-debug version? In which version is "./mtr --debug" implemented?
[2 Feb 2011 8:55]
Bjørn Munch
It does not affect mysqld, try mysqlbinlog. That's the client that failed for me (and still does).
[2 Feb 2011 12:43]
Kristofer Pettersson
ok, got it: thek@goblin:~/bzr/mysql-5.5/bld$ client/mysqlbinlog --debug client/mysqlbinlog: ambiguous option '--debug' (debug-check, debug-info) thek@goblin:~/bzr/mysql-5.5/bld$ client/mysqlbinlog --loose-debug client/mysqlbinlog: ambiguous option '--loose-debug' (--loose-debug-check) My interpretation of the loose prefix is that critical errors which interrupts execution should turn into (at most) warnings when you use the loose-prefix.