|Re: [cdt-dev] Why doesn't DSF-GDB timeout when it submits query?|
Thanks for the quick response, Marc!
I will pay attention to Bug 365601 and contribute as I can – may be testing effort as the bug is not easy to reproduce.
I agree with you that for future usage of DSF Query we should use timeout as possible as we can, especially when we run in the UI thread we can't predict what can go wrong in the background.
Unfortunately it's too late to change the current implementation because there are too many places using the "get()" method now. We can fix them when problems arise.
From: Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Tuesday, 17 July, 2012 1:32 PM
To: "'CDT General developers list.'" <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Why doesn't DSF-GDB timeout when it submits query?
The deadlock below is being worked on as we speak. Please see:
As for using the timeout in query, I'm personally not aware of any reason why
we shouldn't use it. Choosing the right timeout should be done carefully though.
That approach wasn't used when we started and that kind of became the pattern.
We can start introducing such timeouts in different parts as needed.
If you feel that would be helpful, you can file a bug.