Bug #58296 | MTR does no create error log if run with manual-gdb | ||
---|---|---|---|
Submitted: | 18 Nov 2010 18:09 | Modified: | 12 Jan 2011 11:55 |
Reporter: | Sveta Smirnova | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Tools: MTR / mysql-test-run | Severity: | S3 (Non-critical) |
Version: | 5.1-bzr | OS: | Any |
Assigned to: | Bjørn Munch | CPU Architecture: | Any |
[18 Nov 2010 18:09]
Sveta Smirnova
[2 Dec 2010 14:00]
Bjørn Munch
This would be doable, but I'm not sure it is desirable. I would think the debugger (the person I mean) would prefer to get errors and warnings shown in the debugger window? You can't have both. The lines with CURRENT_TEST are written by mtr, not the server.
[2 Dec 2010 17:19]
Sveta Smirnova
Correct. Feel free to close it as !Bg I created this after tested some replication bug where I needed to see errors in slave error log, but was interesting in breakpoints only in master. I could turn logging option in gdb though.
[3 Dec 2010 9:06]
Bjørn Munch
There are three ways to achieve what you want from the current mtr: 1) Add --mysqld==-log-error=<path> to the mtr command line. For some reason, the path must be the full path starting with /, a relative path seems to end up nowhere. 2) The above will affect both servers if you run both master and slave. You can also manually add the --log-error to the gdbinit.mysqld.1 (or .2) file before running the gdb command. 3) Finally, the --log-error may be added to <test>-master.opt or <test>-slave.opt. But please make sure not to commit any such changes! While the existing behavior wasn't coded for but just comes as a consequence of the implementation, it's also IMHO the most useful one. And it can be overridden; should we implement automatic redirection to the error log, I don't know if it would be possible to revert that back to stdout.
[12 Jan 2011 11:55]
Bjørn Munch
Closing to get it off my list.