Bug 368322 - Job not fully stopped when starting non-existing debugger executable
Summary: Job not fully stopped when starting non-existing debugger executable
Status: RESOLVED FIXED
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: debugger (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: 5.1.0
Assignee: Peifeng Yu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-06 10:15 UTC by Kevin Funk
Modified: 2016-09-08 18:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Funk 2016-09-06 10:15:30 UTC 
When trying to debug a program using an debugger which is not installed, KDevelop will not cleanly stop the debug job & return to the Code area.

Reproducible: Always

Steps to Reproduce:
* Select LLDB as debugger
* Don't have lldb-mi installed
* Debug program in KDevelop

Actual Results:  
* You'll get a error popup telling you that lldb-mi is not found (okay)
* The debug job does not exit (not okay)

Expected Results:  
The debug job should exit cleanly, and KDevelop should return to the Code area
Comment 1 Milian Wolff 2016-09-06 20:35:50 UTC 
saw this today as well
Comment 2 Peifeng Yu 2016-09-06 21:05:36 UTC 
It's due to LLDB plugin uses a different code path for error reporting. Working on a fix now.
Comment 3 Peifeng Yu 2016-09-08 17:45:38 UTC 
Fixed in commit b72ece8