Code::Blocks Forums

User forums => General (but related to Code::Blocks) => Topic started by: bbsqterm on June 28, 2010, 10:57:43 pm

Title: F8 and CTRL-F10 have different runtime results
Post by: bbsqterm on June 28, 2010, 10:57:43 pm

CTRL-F10: The instruction at "0x7c9397da" referenced memory at "0x0000000". The memory could not be "read".
F8: Got the correct runtime results.

I think there may be memory leak in my code.
But I cannot locate it because debugging mode (F8) doesn't have that problem.

What should I to fix the problems and make CTRL-F10 has correct runtime results as well.

Thanks.
Title: Re: F8 and CTRL-F10 have different runtime results
Post by: stahta01 on June 28, 2010, 11:12:34 pm
Fix the problems in your logic and other causes of why programs crash.

Tim S.
Title: Re: F8 and CTRL-F10 have different runtime results
Post by: bbsqterm on June 29, 2010, 01:18:55 am
Fix the problems in your logic and other causes of why programs crash.

Tim S.

Usually, the bugs can be located in debug mode [F8].
However, in my case, the F8 works fine, but C-F10 not.
How to locate the bugs which causes C-F10 crashes.?
Title: Re: F8 and CTRL-F10 have different runtime results
Post by: stahta01 on June 29, 2010, 01:33:32 am
You need to find a website that teaches the basic of programming.

FYI:

The debugger does things slightly differently from normal running of a program.
1. It tends to initialize all variables to a default value.
2. It tends to prevent some out of bounds problems from happening
    Example reading or writing past the end of an array.

Tim S.

This is not a site to learn the basics of programming
per the rules: http://forums.codeblocks.org/index.php/topic,9996.0.html
Title: Re: F8 and CTRL-F10 have different runtime results
Post by: Phenom on June 29, 2010, 08:20:55 pm

The instruction at "0x7c9397da" referenced memory at "0x0000000". The memory could not be "read".


This indicates an attemp to use a NULL pointer.