C program can be run under MFCdebug exe abort () has had called-CodePudding

The debug mode there is no problem, but open exe operation error, the debug the error, abort () has had called

CodePudding user response:

Test and operation, KanSi in what place

CodePudding user response:

Put your code commented out first and then let go step by step, until there is an error, then find what went wrong,

CodePudding user response:

reference 1/f, Simple, Soft reply:

debugging operation, where KanSi

The Debug can run normally, but running exe is an error

CodePudding user response:

Screenshots,,

CodePudding user response:

refer to 6th floor Simple - Soft reply:

screenshots,,

CodePudding user response:

refer to the second floor truth is right or wrong response:

your code commented out first, and then let go step by step, until there is an error, then find what went wrong,

too much code and method is not reality

CodePudding user response:

Click retry? 1

CodePudding user response:

refer to the eighth floor Timon - laozhao response:

Quote: refer to the second floor truth is right or wrong response:

Put your code commented out first and then let go step by step, until there is an error, then find what went wrong,

code is too much, method is not realistic

Don't trouble, write their own code, also don't know what?
For example,
Void fun1 ();
Void fun2 ();
,,,,,,
Void fun10 ();
Int main () {
Fun1 ();
,,,,,,

Fun10 ();
} generally true, you put these code all comments/*... */
Wrong operation, not, if not, in turn, put the call function, and see which function calls when there is an error, and can be used within the function also do the same thing, until you find wrong line,

CodePudding user response:

references to the tenth floor truth is right or wrong response:

Quote: refer to the eighth floor Timon - laozhao response:

Quote: refer to the second floor truth is right or wrong response:

Put your code commented out first and then let go step by step, until there is an error, then find what went wrong,

code is too much, method is not realistic

Don't trouble, write their own code, also don't know what?
For example,
Void fun1 ();
Void fun2 ();
,,,,,,
Void fun10 ();
Int main () {
Fun1 ();
,,,,,,

Fun10 ();
} generally true, you put these code all comments/*... */
Wrong operation, not, if not, in turn, put the call function, and see which function calls when there is an error, and can be used within the function also do the same thing, until you find wrong line,

is not what you want to so simple I is an MFC application

CodePudding user response:

Same, you this runtime error, if can't debugging, typically find a wrong version, first and then put a little bit of added functions, until the error, to determine the location of the error,
Otherwise, you debug assembler,
Which is more difficult? Be clear at a glance,
Debugging c + + in practical work, this is a basic debugging skills,

CodePudding user response:

Of course if you confused to write their own code and count me in white said

CodePudding user response:

references 9/f, Simple, Soft reply:

click retry ah 1

not tried

CodePudding user response:

Old, easy brats, I more than a few words of mouth,
Debugging, the first was that can reproduce the error of positioning error, if you can do these two basic no problem too wrong,

CodePudding user response:

On the 14th floor Timon

references - laozhao response:

Quote: references 9/f, Simple, Soft reply:

Click retry ah 1

tried not

Not yet, you have to put the code to me
Qq 3405187170

CodePudding user response:

Click to ignore, and then view the call stack

CodePudding user response:

refer to 17th floor zjq9931 response:

click ignore, and then view the call stack

Not the debug, run the debug, just click the debug exe file can not be run

CodePudding user response:

refer to the 18th floor Timon - laozhao response:

Quote: refer to 17th floor zjq9931 response:
click ignore, and then view the call stack

Not the debug, run the debug, just click the debug exe file can not be run

Then you start to run the program, pop-up a MessageBox.
After running to MessageBox VS menu bar, click on the "debug" - & gt; Attached to the process, and then continue to run, see also won't appear the error,
If appear, it can debug,
If you do not appear, click on the exe file, in this dialog, click retry, or ignored, there is always "debugging" dialog? If don't appear, then increase the log on, step by step or pop-up dialog box, and see which step go wrong, from coarse to fine, located slowly,

CodePudding user response:

Click retry to see the call stack back step by step to your code modifications solution

CodePudding user response:

Has been resolved CV: mat. Reshape errors, can use the debug, directly click the exe is not available

CodePudding user response:

refer to 21st floor Timon - laozhao response:

resolved CV: mat. Reshape appear mistake, can use the debug, directly click the exe unavailable

How to locate the?

CodePudding user response:

Somebody in this problem

CodePudding user response:

reference 23 f Timon - laozhao response:

is the question met

https://blog.csdn.net/xkwnzxxjw/article/details/80659179

Deep copy completely, A=biggest lone (), the method is to reallocate the memory, so you can use the reshape function