Re: MI: -file-list-exec-source-files

[Bob Rossi <bob_rossi@cox.net>]

> Perhaps, but in working on the UI for other debuggers, I have seen this and 
> it looked like the same situation.  When I worked on Compaq ladebug, we had 
> to get the list of source files so that the user could choose one to set 
> bpts in, or to browse.  In retrieving that list from the debugger, I saw e
> xactly what Nick is seeing.  And in delving into the internals of the 
> debugger/compiler, I found that the situation I described, with foo.? to 
> be why I saw more than one source.  This is especially true for C++ when
> templates are used.   What you really want to see in a list like this is 
> "foo.c compiled this way", "foo.c compiled that way", and so on.  I don't 
> think any debugger has solved this problem reasonably from a UI perspective.

Even if this was true, I still think the duplicates make no sense with
the information that -file-list-exec-source-files currently provides.
The front end will use the file as is, so having 1 or N of those files
just makes more I/O at this point.

Bob Rossi