Re: CString oversteps bounds in Release compile
I admit to be "guessing" since there isn't much info to go on. I still
think some of the "bound" is being exceeded and the stack is just ending you
up in this place in the code. I've never seen CString ever have a problem.
I don't think the resources are the problem unless there is one that is just
too long for a CString, but that is unlikely. I also include some .RC files
in my .RC2 file (mostly for libraries that attach to my program) so I fully
understand what you're saying. I also use satellite DLLs though since I
find it the easiest way to extend the program for other languages, but
that's not any kind of religious thing with me :o)
Maybe you could identify just before where the problem is happening and
single step until you find yourself at the location where you think the
problem is happening?
Tom
"AVee" <motion@abilitysystems.com> wrote in message
news:df635dfa-8fdb-4402-a062-c6fc297f534d@25g2000hsx.googlegroups.com...
I'd guess that something else is happening before you get to this code.
Are
you sure your resources are set up correctly (I.E., do you call
AfxSetResourceHandle() or something like that.
Thanks Tom. I do use a lot of resources, but for the sake of the
convenience of having everything in a single executable I don't
compile them into DLL's, but instead #include associated .rc files
from within my .rc2 file ( don't shoot! :-) ). So I don't call
AfxSetResourceHandle(). Perhaps I am exceeding the capacity to do this
(do you know how I might check for this?). Nevertheless, since the
problem in this code starts when CString is instantiated, before it
loads its contents from the resource, inclines me to think that my
resources are intact. But obviously I am missing something.