I just want to thank the team for the work you have done on AVR Studio.
I have previously reported some problems, but I have dealt with HW since, so I have not had the time to test Studio.
The day before yesterday I started RC2 and experienced problems resolving breakpoint addresses in source files located in other directories than the location of the loaded object file. You could step into the code, but not set a breakpoint there.
Today RC3 showed that the problem is solved for my use of it.
Compared to the last time I used AVR Studio much has happened as I see it.
It looks like most of the problems from my last reporting has been solved,
eg. setting breakpoints and locating source seems OK.. But a quick test of "step into"
revealed that call of member functions is OK, while calls of constructors like in this code
some_class_type my_class( param );
just steps over. If I open the assembler window, then I can step into the constructor code.
Another problem report is now documented here in a very small tiny26 program. AVRStudio can not load the program. (see attachment, either attached twice or not attached, I can't see any effect when I click the "Add Attachment" button)
But once more, thank you for the good job on AVR Studio on its way to become one of the best debugging environments available, and for the close contact with the users of your work.
Today I'm glad you were not discouraged by some of the negative comments from the beginning. Nobody creates a tool like this without experiencing problems. Persistence pays off !