Bug 369315

Summary: GDB and Disassemble/Registers tool views duplicate after aborting debugging and starting a new debug launch
Product: [Applications] kdevelop Reporter: Igor Kushnir <igorkuo>
Component: CPP DebuggerAssignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: normal CC: niko.sams
Priority: NOR    
Version First Reported In: git master   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: A warning that appears after starting debugging without finishing the previous debugging session
Duplicated tool views screenshot

Description Igor Kushnir 2016-09-25 09:50:29 UTC 
The number of GDB and Disassemble/Registers tool views at the bottom increments each time after choosing "Yes" in the "A program is already being debugged..." warning dialog.
One can get many copies of these two tool views by repeatedly restarting a debug launch.
The KDevelop window no longer fits the screen width and its window buttons become hidden.
Fortunately the extra tool view copies disappear after restarting KDevelop.

Reproducible: Always

Steps to Reproduce:
1. Start debugging.
2. Start debugging again without finishing the previous debugging session.
3. Click the "Yes" button in the "A program is already being debugged..." warning dialog.

Actual Results:  
There are now two GDB tool views and two Disassemble/Registers tool views at the bottom.
Redundant tool views don't disappear after switching back to the Code mode.

Expected Results:  
Tool views don't duplicate in Debug mode and don't appear in the wrong (Code) mode.
Comment 1 Igor Kushnir 2016-09-25 09:53:03 UTC 
Created attachment 101276 [details]
A warning that appears after starting debugging without finishing the previous debugging session
Comment 2 Igor Kushnir 2016-09-25 09:54:01 UTC 
Created attachment 101277 [details]
Duplicated tool views screenshot
Comment 3 Justin Zobel 2022-10-24 00:46:43 UTC 
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Igor Kushnir 2022-10-24 05:58:33 UTC 
No longer reproducible. Must be fixed.