Yet another release/debug problem...
-
Yeah, I know you guys get this one a lot, I've seen them... But I have another instance of a program running fine in debug and crashing in release. I have set up a configuration that basically mimics as many settings of "release" as possible, but allows me to go through in debug mode and trace code. Ok, here we go: I have a dialog app. The main dialog (we'll call it Dialog A) that opens has a button on it that results in opening Dialog B. Upon clicking this button I get an error of: "The instruction at '0x004229dd' referenced memory at '0x00000401'. The memory could not be 'read'." So I traced it. It occurs AFTER the DialogB::OnInitDialog() call. This is a screenshot of the debug window showing where it 'died' ftp://cabadam.homeip.net/sshot.jpg I am unable to determine why it crashed, maybe one of you guys could help me out. Thanks! Adam cabadam@houston.rr.com
-
Yeah, I know you guys get this one a lot, I've seen them... But I have another instance of a program running fine in debug and crashing in release. I have set up a configuration that basically mimics as many settings of "release" as possible, but allows me to go through in debug mode and trace code. Ok, here we go: I have a dialog app. The main dialog (we'll call it Dialog A) that opens has a button on it that results in opening Dialog B. Upon clicking this button I get an error of: "The instruction at '0x004229dd' referenced memory at '0x00000401'. The memory could not be 'read'." So I traced it. It occurs AFTER the DialogB::OnInitDialog() call. This is a screenshot of the debug window showing where it 'died' ftp://cabadam.homeip.net/sshot.jpg I am unable to determine why it crashed, maybe one of you guys could help me out. Thanks! Adam cabadam@houston.rr.com
m_pCtrlSite contais bogus value. Looks like you're overwriting it somewhere. Do you have access to diagnostic tools like BoundsChecker or Purify? Tomasz Sowinski -- http://www.shooltz.com.pl
