Debugger cli freezes when debugged team exits

[pulkomandy]

Debugger -c ls
co

This runs ls as expected, but ends with this message:

Debugger: Failed to run thread 171718: Bad port ID

Then, it is not possible to interact with Debugger anymore. The prompt doesn't come back, commands don't do anything, even Ctrl+C doesn't work.

Expected behavior: Debugger should either exit, show the debug prompt, or do something similar to the GUI mode with a "do nothing/quit/restart team" prompt.

[pulkomandy]

Forgot to mention: save-report cli command freezes Debugger in a similar way, after saving the report and showing the prompt.

[luroh]

Moving Debugger related tickets out of R1 milestone (Prop #14).

[anevilyak]

The hang on team exit should be addressed in hrev49416. Leaving this open for the other mentioned problems though.

[anevilyak]

(In #12155) Thanks for the update! Please let me know if you run into anything similar again.

• Unlinking #10292 since report saving via the crash dialog is no longer handled via CommandLineUserInterface, so that issue is separate entirely.

[pulkomandy]

A possibly related freeze of Debugger:

~$ Debugger --thread 1359 -c
debugger> bt # works fine
debugger> save-report # works fine
debugger> cont # works fine
debugger> bt
[thread terminated: 1372 "w:1067:app_server cached menu"] # Note: some threads terminating as I do things on display
[thread terminated: 1370 "w:1067:Tâches et activité CPU"]
[thread terminated: 1368 "w:1067:Global Popup cached menu"]
[thread terminated: 1366 "w:1067:Global Popup"]
Current thread is not stopped. Can't get stack trace.

The prompt does not come back, and ctrl+C doesn't work.

I'm using Debugger through ssh to debug some app_server things, so it would be nice to have this working.

I tried to kill Debugger and attach a new instance to the same thread. I did not get to the prompt on this second try and the debugger thread was not stopped (it was still using 100% CPU).