Re: Dialog Editor Crash

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ahhh, yes. But that is the rub. How do I submit a bug report without sample
code to reproduce it. I hve submitted bug reports before and they they don't
get far without it. The problem is the size of the code base. We can't just
send the whole project. It is too big (around 600 Megs).

For some bug reports, I've seen MS request the preprocessor output
files. I don't know if they'd be the right thing in your situation
though.

We can work around
the optimizer problems by inserting pragmas in problem code, which is always
in large subroutines a few hundred lines long.

Are you absolutely sure they're optimizer code-generation problems,
and not incorrect code that happens to give correct results without
the optimizations?

We can't work around Resource
editor crashes in VS2005

Can you reproduce these with smaller resource files or just the
resource files on their own?

Small projects don't have the problems. We just don't know what it is about
our projects that VS6 likes and VS2003/VS2005 doesn't, except that neither
are very happy with large subroutines. If someone can suggest something
better than hoping I'm open to ideas.

Have you tried identifying where in the optimised routine the problem
occurs - down to a line of code? If you could, then the generated
assembly listing would enable someone to determine if it is a
code-generation problem.

Dave
.