Bug #52178 Disable all timeouts when mtr started with --gdb or --client-gdb
Submitted: 18 Mar 2010 12:09 Modified: 7 Feb 2011 14:57
Reporter: Georgi Kodinov Email Updates:
Status: Closed Impact on me:
None 
Category:Tools: MTR / mysql-test-run Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Bjørn Munch CPU Architecture:Any

[18 Mar 2010 12:09] Georgi Kodinov 
Description:
When one tries to debug a test case using mysql-test-run.pl --gdb <test_case> we need to disable all the timeouts so the developers are not forced to debug ... fast.

How to repeat:
Run mysql-test-run.pl --gdb <any test case> make sure the gdb hits a breakpoint and wait there long enough.

Suggested fix:
Disable all the timeouts (or set them to their maximum values so the session doesn't expire when one debugs.
[18 Mar 2010 14:31] MySQL Verification Team 
Thank you for the bug report.
[23 Mar 2010 9:57] Bjørn Munch 
The timeout was set to one week in Bug #45847 (1/10th of that during check-testcase). Are you saying this either isn't working, or is not enough?
[7 Apr 2010 8:39] Georgi Kodinov 
Bernt,

I don't know which timeout occurs. But I've seen this if I ponder in gdb too much.
Can you please just check it ?
[28 Nov 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".
[7 Feb 2011 14:57] Bjørn Munch 
Never got any feedback