Re: variables using ClassView and Class wizard
From: Scott McPhillips [MVP] (scottmcp_at_mvps.org.nothere)
Date: 04/03/04
- Next message: Arnaud Debaene: "Re: C++ integral types on 64-bit Windows"
- Previous message: seia0106: "variables using ClassView and Class wizard"
- In reply to: seia0106: "variables using ClassView and Class wizard"
- Next in thread: seia0106: "Re: variables using ClassView and Class wizard"
- Reply: seia0106: "Re: variables using ClassView and Class wizard"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 03 Apr 2004 14:31:58 -0500
seia0106 wrote:
> Thank you Scott for your reply.
>
> I only have the 'release version' of the program that i am trying to
> improve. Iniitally the breakpoints could not be set. After changing
> project settings in C++ tab to 'program database' and in Linker tab to
> generate debug info the release version can be debugged now.
> But my problem persists. That is when i define a new variable in my
> main class(mytemplateclass<int> X or when i assign variables(of any
> type) to a control(any control) on my MFC GUI, then program runs fine
> and gives correct results but when program exits then above 'access
> violation error' occurs. I wonder if this has something to do with
> Debug/Release. And if it is so how can
> I solve it or what changes i have to made to prject settings or what i
> have to do for making changes to this program, which i only have in
> release mode?
> I am quite new to MFC programming and this problem is puzzling for me.
> Can someone please give some hint what could be causing this error and
> how to fix it? thanks.
Your post shows that there are a couple of basic things about debugging
with VC that you don't understand. There is no such thing as having
only the release version. If you have the code you have what you need to
make a debug version. Investigate the Configurations command on the
Build menu (VC6). You can make a debug build, and it will make analysis
much easier.
Nobody here can tell you where your access violation is occuring. But
the debugger can. If you have not done so, first install the MFC source
code. When the AV occurs study the debugger stack window, and double
click on each call level to learn where the code was executing. You
need to get some information about what is happening, with what, where.
-- Scott McPhillips [VC++ MVP]
- Next message: Arnaud Debaene: "Re: C++ integral types on 64-bit Windows"
- Previous message: seia0106: "variables using ClassView and Class wizard"
- In reply to: seia0106: "variables using ClassView and Class wizard"
- Next in thread: seia0106: "Re: variables using ClassView and Class wizard"
- Reply: seia0106: "Re: variables using ClassView and Class wizard"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
