diff options
| author | Simon Marchi | 2017-02-06 21:53:24 +0000 |
|---|---|---|
| committer | Marc Khouzam | 2017-03-15 20:30:35 +0000 |
| commit | 9b9bc86f2ee79e0e5c33aff58e2c7cd93b68cebd (patch) | |
| tree | ee472583fa1fde0ebaa13cd62d2f5d95995cd9f3 /memory | |
| parent | 4802bf3e16ee4608d0d007e9e4a460cd0cd63769 (diff) | |
| download | org.eclipse.cdt-9b9bc86f2ee79e0e5c33aff58e2c7cd93b68cebd.tar.gz org.eclipse.cdt-9b9bc86f2ee79e0e5c33aff58e2c7cd93b68cebd.tar.xz org.eclipse.cdt-9b9bc86f2ee79e0e5c33aff58e2c7cd93b68cebd.zip | |
Bug 511801 - Remote launch: validate that the remote exec file is absolute
From my experience, bad things happen if the user specifies a
non-absolute path in the box labeled "Remote Absolute File Path for
C/C++ Application". This patch adds a validation to the tab to make
sure that the path is a valid absolute POSIX path.
This assumes that we do not support remote launching on Windows targets,
and therefore do not need to specify paths such as "C:\foo\bar.exe".
Change-Id: I20367078ff20179f0515272afee17d0986940309
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Diffstat (limited to 'memory')
0 files changed, 0 insertions, 0 deletions