| Summary: | Stop execution does not show project name, only configuration | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Ovidiu-Florin BOGDAN <kde.kfoar> |
| Component: | general | Assignee: | Ovidiu-Florin BOGDAN <kde.kfoar> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | kde.kfoar, kfunk |
| Priority: | NOR | Keywords: | junior-jobs |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
FTR: Afaik Ovidiue is working on this already. [11:27] <milian> [21:46:26] ovidiu-florin: setObjectName(launchcfg->name()); in debugjob.cpp:51 [11:27] <milian> [21:46:31] change that and you should be set [11:27] <ovidiu-florin> [21:47:49] milian: how did you get to that? [11:27] <milian> [21:48:17] I knew that we emit a warning when a job is unnamed, thus I grepped for "unnamed" in runcontroller.cpp in kdevplatform/shell/ [11:27] <milian> [21:48:27] that checks the objectName so I knew what to look for in the gdb plugin [11:27] <milian> [21:48:55] the DebugJob sounds like the obvious choice and indeed it's setObjectName does exactly what your status-quo describes Added the project name: https://git.reviewboard.kde.org/r/121171/ I'll study the code some more in order to add the counter. So far, I've noticed that I can't start a second debug session for the same project. Any feedback on this? Fixed in: f98c6e867c5d7d3feda9ef0b559259bea4bdf3f0 |
The stop execution button does not show the Project name of the project being executed, only it's configuration. If I start several projects, with the same configuration name, they are indistinguishable. Reproducible: Always Steps to Reproduce: 1. Setup min. 2 projects with the same run configuration name 2. start them both 3. stop the first one Actual Results: Which is the first one? They both show the same name. Expected Results: Show: {Project Name}: {Run Configuration}{run configuration instance counter} Add a counter in case the same configuration is started several times. I consider this a Junior Job.