Hi Ted,
It looks like you have dug up all the history there is on the Signals view. Perhaps it should have been removed from CDT when CDI was done as clearly no one has taken the time to provided the DSF backend for it in the Open Source version. I can't speak to the decision making beyond that. The only other issues that I can point you at is
Bug 338908 which makes it possible to use Signals view with flexible hierarchy, a prerequisite for DSF support. And
Bug 249220 which was the tracking bug for adding the support, but it has almost no info in it (I have have referenced your email now as that is very useful collection of decision making).
> In which case is there a valid bug there for its removal?
No. We are in the state that someone may be using it. It can be considered under the CDT 10 release perhaps?
@All Is anyone providing Signals view in their own DSF debuggers?
> Is there an equivalent functionality to the signals viewer in CDT today, for a user of CDT wishing to change how the debugger handles a signal is there a current recommended approach?
I think this is a place where the improved Debugger Console integration is a catch all as you can access all GDB functionality that way. While you can do this on Windows, you don't get the nice GDB new-ui implementation. That work still needs to be completed on both the GDB and CDT side last I checked. (I do know of companies with non-GDB based debuggers who are supporting that flow on Windows, so I know CDT is not far from working).
> Is there any appetite to re-enable the Signals Viewer for DSF, or for a pull request that would do that?
I think you are in a better place to answer that question as you probably have some customer demand for it? A tested and complete solution would be welcome, but I am not in a position to comment on how much work that would be.
Thanks
Jonah