Interactive debugging no longer works in old application

[Groundsel]

Hello,

I have been trying to do an interactive debug on a project within a sizable solution (94 projects). I don't think there is anything special about the one chosen. It uses several dll's and is, itself, a "console" application. In the past, I have found many bugs within this solution through interactive debugging and was all set to find another.

However, I got a debugging message "Unable to start program .... Input or output cannot be redirected because the specified file is invalid." Looking at the Output window under debugging were messages for the executable and the dll's "Binary was not built with Debug information."

So I did the following:

1) Rebuild the entire solution. That was no help.
2) Create a Mickey Mouse project from scratch and verify that I can interactively debug. That was OK; so I compared all its Project settings with the one which allegedly had no debug information. There were few settings which were any different. One which I did not match - for implementation reasons - was placement of the pdb file in the same folder as the executable. However, that has not been a problem in the past.

So I am puzzled. Before I log this with technical support, I thought I would ask if there are any other set-up defaults which, when applied in conjunction with the new Composer XE compilers could cause this. I hope I am not asking something already answered which has escaped my search.

[Steven_L_Intel1]

What do you have in the Debugging property page?

[Groundsel]

Please delete this thread. My error was in thinking that the message about the binaries was current. The actual (trivial) error was in the name of the redirected input file. It would have been better if the message had said "does not exist" rather than "is illegal". Anyway, sorry to have asked such a question and to have wasted most of a day in looking for more complexity than existed.