Bug 251530 - Debugger cannot open executable paths that are not escaped in the launcher configuration
Summary: Debugger cannot open executable paths that are not escaped in the launcher co...
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: 4.0.80
Platform: openSUSE Linux
: NOR minor
Target Milestone: 4.1.0
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-17 06:15 UTC by Ramón Zarazúa
Modified: 2011-06-12 17:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.3.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ramón Zarazúa 2010-09-17 06:15:45 UTC 
Version:           4.0.80 (using KDE 4.5.0) 
OS:                Linux

When trying to debug a program via a launch configuration that has an absolute executable path, the debugger will not run if the path is not escaped(escaping spaces with \ for example).

Reproducible: Always

Steps to Reproduce:

Reproduction steps:
-Open a Makefile project
-Create a new launch configuration
-Specify the absolute path to an executable that has a space in the path
-Attempt to debug the program(Via Run->Execute Launch

Actual Results:  
Debugger will not start, will complain that the path does not exist

Expected Results:  
Debug the program
Comment 1 damien.porquet 2010-10-13 12:41:21 UTC 
Same problem here.
As a workaround it's also possible to enclose the path with "".
D.
Comment 2 Niko Sams 2011-06-12 17:45:00 UTC 
Git commit e7e264b84e3751acfdce419f4294c913a149e8bb by Niko Sams.
Committed on 12/06/2011 at 17:43.
Pushed by nsams into branch 'master'.

Quote paths to not fail on paths with spaces

BUG: 251530

M  +7    -7    debuggers/gdb/debugsession.cpp     

http://commits.kde.org/kdevelop/e7e264b84e3751acfdce419f4294c913a149e8bb