[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cdt-dev] DSF timeouts
- From: Vladimir Prus <vladimir@xxxxxxxxxxxxxxxx>
- Date: Wed, 29 Jun 2011 19:20:35 +0400
- Delivered-to: email@example.com
- Organization: CodeSourcery
- User-agent: KMail/1.13.6 (Linux/2.6.38-8-generic-pae; KDE/4.6.2; i686; ; )
On Monday, June 27, 2011 18:27:21 Marc Khouzam wrote:
> > -----Original Message-----
> > From: cdt-dev-bounces@xxxxxxxxxxx
> > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vladimir Prus
> > Sent: Friday, June 24, 2011 1:50 PM
> > To: cdt-dev@xxxxxxxxxxx
> > Subject: [cdt-dev] DSF timeouts
> > Hello,
> > some time ago I've asked whether DSF has, in general, timeouts for all
> > GDB commands that it sends:
> > http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg19523.html
> > I was pointed to a specific Bugzilla issue about 'interrupt' command:
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=310274
> > and that specific issue was fixed, but I'm having trouble
> > understanding
> > whether, in current DSF HEAD:
> > 1. There's always some timeout for every single command sent to GDB.
> No, we don't have that. It has been suggested before and I think it
> would add a another level of safety, but it has not proven urgent
> enough for anyone to contribut it.
Do you have a suggestion where such logic can be added?
> > 2. There's a timeout for the launch sequence as a whole.
> There is a 30 second timeout for GDB to be started.
> However, the rest of the launch sequence does not have a timeout.
> I don't think it would be very hard to add, probably in GdbLaunchDelegate.
Again, could you suggest the best way? It seems that ideally, the 'execute'
method of the executor would have a timeout parameter.
CodeSourcery / Mentor Graphics
+7 (812) 677-68-40