Why would lead to the memory default order printf (coredump)? ? ? Can you heroes, I would call a procedural Lane function, defined in another document, in which the printf function if it can operate normally, but will not print default procedures will produce memory (coredump) errors are so numerous test, The problem lies not know where, in theory memory printf nothing wrong with the bar, really can not understand why, you see heroes guidance on January 2, FOSS issues are as follows : LRet=InitAgainVsSeria (pVsSerialInfo, &pVsSerialHead, &strErrorRec.lSqlCode); Another function is defined as the document InitAgainVsSeria Long InitAgainVsSerial (VS_SERIAL_INFO *pVsSerialInfo, VS_RECORD_HEAD **ppVsSerialHead, long *plSqlCode) ( Long lRet=0; VS_RECORD_HEAD *pVsSerialHead=NULL; ERROR_REC strErrorRec;                 LRet=tblInsAgainVsSerial (pVsSerialInfo);         [b][i]#ifdef DEBUG Printf ( "tblInsAgainVsSerial 's result:lRet=%d\n" lRet); #endif [/i][/b] If (lRet!=ERROR_SUCCESS) ( StrErrorRec.lErrCode=lRet; Getapperrmsg (&strErrorRec); *plSqlCode=lRet; Printf ( "water bar AgainVs insertion sequence wrong message : %s.SQL code : %ld.\n wrong reasons : %s. \n Address : %s. \n "StrErrorRec.sErrMessage, strErrorRec.lSqlCode. strErrorRec.sCause, strErrorRec.sAction); Userlog ( "water bar AgainVs insertion sequence wrong message : %s.SQL code : %ld.\n wrong reasons : %s. \n Address : %s. \n "StrErrorRec.sErrMessage, strErrorRec.lSqlCode. strErrorRec.sCause, strErrorRec.sAction); Return (VS_AGAIN_SERIAL_INS_ERR);         }                         Return (NO_ERROR); } Crude italics in the wrong place on the open printf normal operations, on being given the customs! Em14 : : Why would lead to the memory default order printf (coredump)? ? ? Find indicator variables Why would lead to the memory default order printf (coredump)? ? ? Oh, can express Argentina? Read indicator variables, we see what has gone wrong, but if you open the operation of the printf Guidelines from the variable values are absolutely correct. Why would lead to the memory default order printf (coredump)? ? ? : Cry : Why would lead to the memory default order printf (coredump)? ? ? May : Elsewhere (CALL function before), there have long been in violation of the procedure, in which the show. Printf you with a chorus, not good, not just dump it. Zhushidiao first block if you look at the results. Why would lead to the memory default order printf (coredump)? ? ? Thank you can return, but has not yet been settled During Zhushidiao if there will be the default memory error Oh, look green eyes : shock : Why would lead to the memory default order printf (coredump)? ? ? Then you keep memory fault, the investigation forward. Also, You are not in the definition of a function before the procedure in many large array? Why would lead to the memory default order printf (coredump)? ? ? In tblInsAgainVsSerial internal problem, in fact tblInsAgainVsSerial internally on the memory overflow. If the test is reliable tblInsAgainVsSerial function, it can only be a possible target : pVsSerialInfo not point to one entity. In addition, the defined function InitAgainVsSerial pVsSerialHead were doing? Not used ah? Imported parameters ppVsSerialHead also seemed redundant. [ Closed window ]