Problem with Release verison

I have an mfc executable (say myexe) developed on 5.0.
Myexe launches an mfc extension dll mydll (developed on 5.0).
Through a menu Item on Myexe we can invoke the
extension classes stored in mydll ( an mdisplitter window
with Ctreeview, CListview and lots of dialogs.I use
Mdisplitterwnd::Create function)
The debug verion runs fine. In the release build
the application fails when i invoke  mfc extension classes
repeatedly .( some times in 3rd attempt or 4th attempt).
Please suggest where do i start debugging ?
Or any special cases to consider  in this type of setup ?
One more thing, I am not using document template
to bind my frame window, Views and document class.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MFC123Author Commented:
Edited text of question.
Start debugging by reproducing the problem under the debugger!  Sheesh; what could be more obvious?

In what area do you need advice? Do you not know how to debug a release build? Do you not know how to debug?

Exactly what kind of "failure" are you getting?

..B ekiM
MFC123Author Commented:

As i said the debug verion is fine.
Is it possible to step thru the code using release verion ?

The error is something like this
" the instruction referrenced memmory at "0X03.........f".
memory couldn't be written.

I get this error when i click on the menu item 3rd or 4th time
( clicking on menu item will create the mdi splitter window
from extension classes stored in the DLL)

Any comments are highly welcomed

Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

MFC123Author Commented:
Adjusted points to 30
Look at here is article about debugging release build.
I've run into the same problem before.  For me it was one of my event handlers did not declare the lparam, wparam in the .h as it should have.  The debug version did not have a problem with this, but the release version did.  Hope that helps.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MFC123Author Commented:
hi jpick:
i too feel the problem could be with event handler.
let me jus check out in detail . Thanks a lot for the
> Is it possible to step thru the code using release verion ?


1) Add a new project configuration; base it on your existing release build.

2) Modify the "debug info" settings on the C/C++ tab to create a program database.

3) Modify the linker settings to emit debug information.

4) Debug!

..B ekiM
Where does this stand?  Did you debug the app yet?

..B ekiM
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Programming

From novice to tech pro — start learning today.