Using VB to do a small program, the PDF files saved to the database, often is saved to a database error "insufficient memory", and then quit, what possible reason would appear this error

CodePudding user response:

Collapsed in the pop-up dialog box, press the corresponding button to enter debugging press Alt + 7 key to view the Call Stack, namely "the Call Stack" from the inside to the following out of from the inner to outer function Call history, double-click a row to the cursor to the Call of the source code or assembly instruction, don't understand when double click on the next line, until we can read ,

Please judge the return value of each function call,

CodePudding user response:

reference 1st floor zhao4zhong1 response:

collapsed in the pop-up dialog box, press the corresponding button to enter debugging press Alt + 7 view the Call Stack that is "the Call Stack" from the inside to the following out of from the inner to outer function Call history, double-click a row to the cursor to the Call of the source code or assembly instruction, don't understand when double click on the next line, until we can read ,

Please judge the return values of each function call

With, what stuff so high?

CodePudding user response:

refer to the second floor xiaoyao961 response:

Quote: refer to 1st floor zhao4zhong1 response:

Collapsed in the pop-up dialog box, press the corresponding button to enter debugging press Alt + 7 key to view the Call Stack, namely "the Call Stack" from the inside to the following out of from the inner to outer function Call history, double-click a row to the cursor to the Call of the source code or assembly instruction, don't understand when double click on the next line, until we can read ,

Please judge the return values of each function call

With, what stuff so high?

WinDbg namely was Debugging Tools for Windows

CodePudding user response:

refer to the second floor xiaoyao961 response:

Quote: refer to 1st floor zhao4zhong1 response:

Collapsed in the pop-up dialog box, press the corresponding button to enter debugging press Alt + 7 key to view the Call Stack, namely "the Call Stack" from the inside to the following out of from the inner to outer function Call history, double-click a row to the cursor to the Call of the source code or assembly instruction, don't understand when double click on the next line, until we can read ,

Please judge the return values of each function call

With, what stuff so high?

VB6 also have this stuff, you focus on VB for 13 years, also don't know?

Under the IDE to run the program, code execution is breakpoint "break", press Ctrl + L, pop up a small window,
In this window "list" can be seen here "" from which the invocation of,
The first line is "the innermost", is the breakpoint function or procedure,
The last line is "the outermost layer", is "the most began to call" statement process,
In addition to "the innermost", in the "top" of the code in the module has a "green mark" is where the "call" instructions,
In the "widget", double click on the corresponding process can jump to the corresponding call statement,