DESCRIPTION

gdbtrace: Prevent hang when GDB stops responding by using timeouts

Bug: 415728
Change-Id: I6eacb9680f4966183a24c5ad915e4ddff256f40d
Signed-off-by: Alivia Ritter xxx@xxx.xxx


COMMENTS

author: Kaeden Tapia
date: 2014-03-06 23:00:43.000000000

Uploaded patch set 1.

-------------------------------------
author: Brenden Conley
date: 2014-03-07 00:23:47.000000000

Patch Set 1:

Build Started https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/5814/

-------------------------------------
author: Brenden Conley
date: 2014-03-07 01:21:45.000000000

Patch Set 1: Verified+1

Build Successful 

https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/5814/ : SUCCESS

-------------------------------------
author: Ricky Reeves
date: 2014-03-07 14:36:34.000000000

Patch Set 1:

I'm not able to reproduce the issue in the bug report. However, I loaded a GDB trace in my environment and it worked fine. Is 1 second enough? CDT has a default of 10 seconds (which I would see as too much).

-------------------------------------
