Re: [sqlite] TCL Test failures on ARM
Appreciate if someone can point out what’s going wrong with these tests -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67707.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
Does it have anything to do with platform ? i am not sure though , because i am new to ARM and sqlite. Thanks Brijesh -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67709.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
Hi,
Below is the code sequence after making a breakpoint at robust_ftruncate()
i could see that robust_ftruncate and ts_ftruncate is called couple of
times before the error is given to the user
Breakpoint 2, ts_ftruncate (fd=5, n=297136) at ./src/test_syscall.c:273
273 if( tsIsFailErrno(ftruncate) ){
(gdb) break robust_ftruncate
Breakpoint 3 at 0x66b14: file sqlite3.c, line 23589.
(gdb) continue
Continuing.
Breakpoint 3, robust_ftruncate (h=6, sz=0) at sqlite3.c:23589
23589 do{ rc = osFtruncate(h,sz); }while( rc0 errno==EINTR );
(gdb) next
Breakpoint 2, ts_ftruncate (fd=6, n=297136) at ./src/test_syscall.c:273
273 if( tsIsFailErrno(ftruncate) ){
(gdb)
276 return orig_ftruncate(fd, n);
(gdb)
277 }
(gdb)
robust_ftruncate (h=6, sz=0) at sqlite3.c:23590
23590 return rc;
(gdb)
23591 }
(gdb)
unixTruncate (id=0x14c660, nByte=0) at sqlite3.c:26364
26364 if( rc ){
(gdb)
26365 pFile-lastErrno = errno;
(gdb)
26366 return unixLogError(SQLITE_IOERR_TRUNCATE, ftruncate,
pFile-zPath);
(gdb)
26383 }
(gdb)
sqlite3OsTruncate (id=0x14c660, size=0) at sqlite3.c:15035
15035 }
(gdb)
pager_end_transaction (pPager=0x14c4c8, hasMaster=1, bCommit=1)
at sqlite3.c:39296
39296 pPager-journalOff = 0;
(gdb)
39331 sqlite3BitvecDestroy(pPager-pInJournal);
(gdb)
39332 pPager-pInJournal = 0;
(gdb)
39333 pPager-nRec = 0;
(gdb)
39334 sqlite3PcacheCleanAll(pPager-pPCache);
(gdb)
39335 sqlite3PcacheTruncate(pPager-pPCache, pPager-dbSize);
(gdb)
39337 if( pagerUseWal(pPager) ){
(gdb)
39344 }else if( rc==SQLITE_OK bCommit
pPager-dbFileSizepPager-dbSize ){
(gdb)
39355 if( !pPager-exclusiveMode
(gdb)
39356 (!pagerUseWal(pPager) || sqlite3WalExclusiveMode(pPager-pWal,
0))
(gdb)
39358 rc2 = pagerUnlockDb(pPager, SHARED_LOCK);
(gdb)
39359 pPager-changeCountDone = 0;
(gdb)
39361 pPager-eState = PAGER_READER;
(gdb)
39362 pPager-setMaster = 0;
(gdb)
39364 return (rc==SQLITE_OK?rc2:rc);
(gdb)
39365 }
(gdb)
sqlite3PagerCommitPhaseTwo (pPager=0x14c4c8) at sqlite3.c:43389
43389 return pager_error(pPager, rc);
(gdb)
43390 }
(gdb)
sqlite3BtreeCommitPhaseTwo (p=0x162b70, bCleanup=1) at sqlite3.c:51637
51637 if( rc!=SQLITE_OK bCleanup==0 ){
(gdb)
51641 pBt-inTransaction = TRANS_READ;
(gdb)
51644 btreeEndTransaction(p);
(gdb)
51645 sqlite3BtreeLeave(p);
(gdb)
51646 return SQLITE_OK;
(gdb)
51647 }
(gdb)
vdbeCommit (db=0x16bad0, p=0x164ab8) at sqlite3.c:60633
60633 for(i=0; idb-nDb; i++){
(gdb)
60639 sqlite3EndBenignMalloc();
(gdb)
60640 enable_simulated_io_errors();
(gdb)
60642 sqlite3VtabCommit(db);
(gdb)
60646 return rc;
(gdb)
60647 }
(gdb)
sqlite3VdbeHalt (p=0x164ab8) at sqlite3.c:60879
60879 if( rc==SQLITE_BUSY p-readOnly ){
(gdb)
60882 }else if( rc!=SQLITE_OK ){
(gdb)
60886 db-nDeferredCons = 0;
(gdb)
60887 sqlite3CommitInternalChanges(db);
(gdb)
60879 if( rc==SQLITE_BUSY p-readOnly ){
(gdb)
60892 db-nStatement = 0;
(gdb)
60911 if( eStatementOp ){
(gdb)
60928 if( p-changeCntOn ){
(gdb)
60938 sqlite3VdbeLeave(p);
(gdb)
60942 if( p-pc=0 ){
(gdb)
60943 db-activeVdbeCnt--;
(gdb)
60944 if( !p-readOnly ){
(gdb)
60949 p-magic = VDBE_MAGIC_HALT;
(gdb)
60951 if( p-db-mallocFailed ){
(gdb)
60964 return (p-rc==SQLITE_BUSY ? SQLITE_BUSY : SQLITE_OK);
(gdb)
60965 }
(gdb)
sqlite3VdbeExec (p=0x164ab8) at sqlite3.c:66964
66964 sqlite3CloseSavepoints(db);
(gdb)
66965 if( p-rc==SQLITE_OK ){
(gdb)
66966 rc = SQLITE_DONE;
(gdb)
66970 goto vdbe_return;
(gdb)
70404 db-lastRowid = lastRowid;
(gdb)
70405 sqlite3VdbeLeave(p);
(gdb)
70406 return rc;
(gdb)
70444 }
(gdb)
sqlite3Step (p=0x164ab8) at sqlite3.c:62345
62345 db-vdbeExecCnt--;
(gdb)
62351 if( rc!=SQLITE_ROW db-xProfile !db-init.busy p-zSql ){
(gdb)
62358 if( rc==SQLITE_DONE ){
(gdb)
62360 p-rc = doWalCallbacks(db);
(gdb)
62361 if( p-rc!=SQLITE_OK ){
(gdb)
62366 db-errCode = rc;
(gdb)
62367 if( SQLITE_NOMEM==sqlite3ApiExit(p-db, p-rc) ){
(gdb)
62382 if( p-isPrepareV2 rc!=SQLITE_ROW rc!=SQLITE_DONE ){
(gdb)
62389 return (rcdb-errMask);
(gdb)
62390 }
(gdb)
sqlite3_step (pStmt=0x164ab8) at sqlite3.c:62425
62425 if( rc2!=SQLITE_OK ALWAYS(v-isPrepareV2) ALWAYS(db-pErr) ){
(gdb)
62444 rc = sqlite3ApiExit(db, rc);
(gdb)
62445 sqlite3_mutex_leave(db-mutex);
(gdb)
62446 return rc;
(gdb)
62447 }
(gdb)
dbEvalStep (p=0x7efff1a0) at ./src/tclsqlite.c:1401
1401 if( rcs==SQLITE_ROW ){
(gdb)
1404 if( p-pArray ){
(gdb)
1407 rcs = sqlite3_reset(pStmt);
(gdb)
1409 pDb-nStep =
sqlite3_stmt_status(pStmt,SQLITE_STMTSTATUS_FULLSCAN_STEP,1);
(gdb)
1410 pDb-nSort =
Re: [sqlite] TCL Test failures on ARM
Above code / details helps to understand the problem ??? -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67699.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
Details provided helps to understand the problem ?
while executing below line the failures are created.
faultsim_test_result {0 {abc def ghi truncate abc def ghi jkl mno pqr 2}}
i tried debugging this issue but could not really succeed.
Thank you
Brijesh
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67700.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
below is the backtrace after first hit at robust_ftruncate() (first hit after
ts_ftruncate())
Breakpoint 1, ts_ftruncate (fd=5, n=297136)
at ./src/test_syscall.c:273
273 if( tsIsFailErrno(ftruncate) ){
(gdb) break robust_ftruncate
Breakpoint 2 at 0x66b14: file sqlite3.c, line 23589.
(gdb) continue
Continuing.
Breakpoint 2, robust_ftruncate (h=6, sz=0) at sqlite3.c:23589
23589 do{ rc = osFtruncate(h,sz); }while( rc0 errno==EINTR );
(gdb) backtrace
#0 robust_ftruncate (h=6, sz=0) at sqlite3.c:23589
#1 0x00068ba8 in unixTruncate (id=0x162368, nByte=0)
at sqlite3.c:26363
#2 0x0005c5b0 in sqlite3OsTruncate (id=0x162368, size=0)
at sqlite3.c:15034
#3 0x00070c0c in pager_end_transaction (pPager=0x1621d0,
hasMaster=1, bCommit=1) at sqlite3.c:39294
#4 0x00075da4 in sqlite3PagerCommitPhaseTwo (pPager=0x1621d0)
at sqlite3.c:43388
#5 0x000813f8 in sqlite3BtreeCommitPhaseTwo (p=0x15be50,
bCleanup=1) at sqlite3.c:51636
#6 0x00092094 in vdbeCommit (db=0x16bad0, p=0x163620)
at sqlite3.c:60636
#7 0x000925cc in sqlite3VdbeHalt (p=0x163620) at sqlite3.c:60877
#8 0x0009ba98 in sqlite3VdbeExec (p=0x163620) at sqlite3.c:66956
#9 0x00094fd4 in sqlite3Step (p=0x163620) at sqlite3.c:62344
#10 0x00095218 in sqlite3_step (pStmt=0x163620)
at sqlite3.c:62418
#11 0x0005314c in dbEvalStep (p=0x7efff1a0)
at ./src/tclsqlite.c:1400
#12 0x00054eb0 in DbObjCmd (cd=0x17f358, interp=0x122198,
---Type return to continue, or q return to quit---
objc=3, objv=0x12302c) at ./src/tclsqlite.c:2251
#13 0x2aaf4348 in ?? ()
#14 0x2aaf4348 in ?? ()
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67703.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
Below is the backtrace from the gdb when the failure happened. #0 tsIsFail () at ./src/test_syscall.c:163 #1 0x000324b4 in tsIsFailErrno (zFunc=0xc8920 ftruncate) at ./src/test_syscall.c:196 #2 0x0003268c in ts_ftruncate (fd=5, n=206456) at ./src/test_syscall.c:273 #3 0x000627f0 in robust_ftruncate (sz=0, h=5) at sqlite3.c:23589 #4 unixTruncate (nByte=0, id=0x12f2e0) at sqlite3.c:26363 #5 unixTruncate (id=0x12f2e0, nByte=optimized out) at sqlite3.c:26348 #6 0x00069284 in sqlite3OsTruncate (size=0, id=0x12f2e0) at sqlite3.c:15034 #7 pager_end_transaction (pPager=0x12f148, hasMaster=optimized out, bCommit=1) at sqlite3.c:39294 #8 0x0006945c in sqlite3PagerCommitPhaseTwo (pPager=0x12f148) at sqlite3.c:43388 #9 0x0007a5dc in sqlite3BtreeCommitPhaseTwo (bCleanup=0, p=0x131e50) at sqlite3.c:51636 #10 sqlite3BtreeCommitPhaseTwo (p=0x131e50, bCleanup=0) at sqlite3.c:51622 #11 0x0008bd2c in vdbeCommit (p=0x131c88, db=0x14c6c0) at sqlite3.c:60488 #12 sqlite3VdbeHalt (p=0x131c88) at sqlite3.c:60877 #13 0x000b6a84 in sqlite3VdbeExec (p=0x131c88) at sqlite3.c:64906 #14 0x000a50b8 in sqlite3Step (p=0x131c88) at sqlite3.c:62344 #15 sqlite3_step (pStmt=optimized out) at sqlite3.c:62418 #16 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400 #17 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198, objc=optimized out, objv=0x10802c) at ./src/tclsqlite.c:2251 (gdb) backtrace #0 unixTruncate (nByte=0, id=0x12f2e0) at sqlite3.c:26366 #1 unixTruncate (id=0x12f2e0, nByte=optimized out) at sqlite3.c:26348 #2 0x00069284 in sqlite3OsTruncate (size=0, id=0x12f2e0) at sqlite3.c:15034 #3 pager_end_transaction (pPager=0x12f148, hasMaster=optimized out, bCommit=1) at sqlite3.c:39294 #4 0x0006945c in sqlite3PagerCommitPhaseTwo (pPager=0x12f148) at sqlite3.c:43388 #5 0x0007a5dc in sqlite3BtreeCommitPhaseTwo (bCleanup=0, p=0x131e50) at sqlite3.c:51636 #6 sqlite3BtreeCommitPhaseTwo (p=0x131e50, bCleanup=0) at sqlite3.c:51622 #7 0x0008bd2c in vdbeCommit (p=0x131c88, db=0x14c6c0) at sqlite3.c:60488 #8 sqlite3VdbeHalt (p=0x131c88) at sqlite3.c:60877 #9 0x000b6a84 in sqlite3VdbeExec (p=0x131c88) at sqlite3.c:64906 #10 0x000a50b8 in sqlite3Step (p=0x131c88) at sqlite3.c:62344 #11 sqlite3_step (pStmt=optimized out) at sqlite3.c:62418 #12 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400 #13 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198, objc=optimized out, objv=0x10802c) at ./src/tclsqlite.c:2251 #14 0x2aaf4348 in ?? () #15 0x2aaf4348 in ?? () (gdb) backtrace #0 unixLogErrorAtLine (errcode=1546, zFunc=0xc8920 ftruncate, zPath=0x12f350 /home/brijesh/mySQLtry/test.db-journal, iLine=26366) at sqlite3.c:23979 #1 0x00069284 in sqlite3OsTruncate (size=0, id=0x12f2e0) at sqlite3.c:15034 #2 pager_end_transaction (pPager=0x12f148, hasMaster=optimized out, bCommit=1) at sqlite3.c:39294 #3 0x0006945c in sqlite3PagerCommitPhaseTwo (pPager=0x12f148) at sqlite3.c:43388 #4 0x0007a5dc in sqlite3BtreeCommitPhaseTwo (bCleanup=0, p=0x131e50) at sqlite3.c:51636 #5 sqlite3BtreeCommitPhaseTwo (p=0x131e50, bCleanup=0) at sqlite3.c:51622 #6 0x0008bd2c in vdbeCommit (p=0x131c88, db=0x14c6c0) at sqlite3.c:60488 #7 sqlite3VdbeHalt (p=0x131c88) at sqlite3.c:60877 #8 0x000b6a84 in sqlite3VdbeExec (p=0x131c88) at sqlite3.c:64906 #9 0x000a50b8 in sqlite3Step (p=0x131c88) at sqlite3.c:62344 #10 sqlite3_step (pStmt=optimized out) at sqlite3.c:62418 #11 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400 #12 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198, objc=optimized out, objv=0x10802c) at ./src/tclsqlite.c:2251 #13 0x2aaf4348 in ?? () #14 0x2aaf4348 in ?? () #0 sqlite3Step (p=optimized out) at sqlite3.c:62366 #1 sqlite3_step (pStmt=optimized out) at sqlite3.c:62418 #2 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400 #3 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198, objc=optimized out, objv=0x10802c) at ./src/tclsqlite.c:2251 #4 0x2aaf4348 in ?? () #5 0x2aaf4348 in ?? () -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67641.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
Below are the code path which is getting executed from the first hit of
breakpoint at ts_ftruncate to the next
i was wondering it was working fine with my ubuntu PC and now giving issue
in linux target.
Breakpoint 1, ts_ftruncate (fd=5, n=206456) at ./src/test_syscall.c:272
272 static int ts_ftruncate(int fd, off_t n){
(gdb) step
273 if( tsIsFailErrno(ftruncate) ){
(gdb) next
272 static int ts_ftruncate(int fd, off_t n){
(gdb)
273 if( tsIsFailErrno(ftruncate) ){
(gdb)
276 return orig_ftruncate(fd, n);
(gdb)
unixTruncate (nByte=0, id=0x14c478) at sqlite3.c:26365
26365 pFile-lastErrno = errno;
(gdb)
26366 return unixLogError(SQLITE_IOERR_TRUNCATE, ftruncate,
pFile-zPath);
(gdb)
unixTruncate (id=0x14c478, nByte=optimized out) at sqlite3.c:26383
26383 }
(gdb)
unixTruncate (id=0x1, nByte=optimized out) at sqlite3.c:26348
26348 static int unixTruncate(sqlite3_file *id, i64 nByte){
(gdb)
unixLogErrorAtLine (errcode=1546, zFunc=0xc8920 ftruncate,
zPath=0x14c4e8 /home/brijesh/mySQLtry/test.db-journal, iLine=26366)
at sqlite3.c:23979
23979 ){
(gdb)
23981 int iErrno = errno; /* Saved syscall error number */
(gdb)
24017 assert( errcode!=SQLITE_OK );
(gdb)
23981 int iErrno = errno; /* Saved syscall error number */
(gdb)
24017 assert( errcode!=SQLITE_OK );
(gdb)
24018 if( zPath==0 ) zPath = ;
(gdb)
24019 sqlite3_log(errcode,
(gdb)
24018 if( zPath==0 ) zPath = ;
(gdb)
24019 sqlite3_log(errcode,
(gdb)
24025 }
(gdb)
pager_end_transaction (pPager=0x14c2e0, hasMaster=optimized out,
bCommit=1)
at sqlite3.c:39301
39301 pPager-journalOff = 0;
(gdb)
39331 sqlite3BitvecDestroy(pPager-pInJournal);
(gdb)
39332 pPager-pInJournal = 0;
(gdb)
39334 sqlite3PcacheCleanAll(pPager-pPCache);
(gdb)
39332 pPager-pInJournal = 0;
(gdb)
39333 pPager-nRec = 0;
(gdb)
39334 sqlite3PcacheCleanAll(pPager-pPCache);
(gdb)
39335 sqlite3PcacheTruncate(pPager-pPCache, pPager-dbSize);
(gdb)
39337 if( pagerUseWal(pPager) ){
(gdb)
39344 }else if( rc==SQLITE_OK bCommit
pPager-dbFileSizepPager-dbSize ){
(gdb)
39355 if( !pPager-exclusiveMode
(gdb)
39356 (!pagerUseWal(pPager) || sqlite3WalExclusiveMode(pPager-pWal,
0))
(gdb)
39358 rc2 = pagerUnlockDb(pPager, SHARED_LOCK);
(gdb)
39359 pPager-changeCountDone = 0;
(gdb)
39364 return (rc==SQLITE_OK?rc2:rc);
(gdb)
39361 pPager-eState = PAGER_READER;
(gdb)
39364 return (rc==SQLITE_OK?rc2:rc);
(gdb)
39361 pPager-eState = PAGER_READER;
(gdb)
39362 pPager-setMaster = 0;
(gdb)
39365 }
(gdb)
sqlite3PagerCommitPhaseTwo (pPager=0x14c2e0) at sqlite3.c:43389
43389 return pager_error(pPager, rc);
(gdb)
43390 }
(gdb)
sqlite3PagerCommitPhaseTwo (pPager=0x1424c8) at sqlite3.c:43389
43389 return pager_error(pPager, rc);
(gdb)
pager_error (pPager=0x14c2e0, rc=1546) at sqlite3.c:39190
39190 assert( rc==SQLITE_OK || !MEMDB );
(gdb)
39188 static int pager_error(Pager *pPager, int rc){
(gdb)
39190 assert( rc==SQLITE_OK || !MEMDB );
(gdb)
39191 assert(
(gdb)
39189 int rc2 = rc 0xff;
(gdb)
39196 if( rc2==SQLITE_FULL || rc2==SQLITE_IOERR ){
(gdb)
39198 pPager-eState = PAGER_ERROR;
(gdb)
39201 }
(gdb)
sqlite3BtreeCommitPhaseTwo (bCleanup=1, p=0x1424c8) at sqlite3.c:51637
51637 if( rc!=SQLITE_OK bCleanup==0 ){
(gdb)
51641 pBt-inTransaction = TRANS_READ;
(gdb)
51637 if( rc!=SQLITE_OK bCleanup==0 ){
(gdb)
51644 btreeEndTransaction(p);
(gdb)
51646 return SQLITE_OK;
(gdb)
51644 btreeEndTransaction(p);
(gdb)
51645 sqlite3BtreeLeave(p);
(gdb)
sqlite3BtreeCommitPhaseTwo (p=0x1424c8, bCleanup=1) at sqlite3.c:51647
51647 }
(gdb)
vdbeCommit (p=0x132040, db=0x140ea8) at sqlite3.c:60633
60633 for(i=0; idb-nDb; i++){
(gdb)
60634 Btree *pBt = db-aDb[i].pBt;
(gdb)
60635 if( pBt ){
(gdb)
60633 for(i=0; idb-nDb; i++){
(gdb)
60634 Btree *pBt = db-aDb[i].pBt;
(gdb)
60635 if( pBt ){
(gdb)
60636 sqlite3BtreeCommitPhaseTwo(pBt, 1);
(gdb)
Breakpoint 1, ts_ftruncate (fd=6, n=206456) at ./src/test_syscall.c:272
272 static int ts_ftruncate(int fd, off_t n){
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67659.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
below is the stack trace at the begining of second hit at the break point
Breakpoint 1, ts_ftruncate (fd=6, n=206456) at ./src/test_syscall.c:272
272 static int ts_ftruncate(int fd, off_t n){
(gdb) backtrace
#0 ts_ftruncate (fd=6, n=206456) at ./src/test_syscall.c:272
#1 0x000627f0 in robust_ftruncate (sz=0, h=6) at sqlite3.c:23589
#2 unixTruncate (nByte=0, id=0x150b60) at sqlite3.c:26363
#3 unixTruncate (id=0x150b60, nByte=optimized out) at sqlite3.c:26348
#4 0x00069284 in sqlite3OsTruncate (size=0, id=0x150b60) at sqlite3.c:15034
#5 pager_end_transaction (pPager=0x1509c8, hasMaster=optimized out,
bCommit=1) at sqlite3.c:39294
#6 0x0006945c in sqlite3PagerCommitPhaseTwo (pPager=0x1509c8)
at sqlite3.c:43388
#7 0x0007a5dc in sqlite3BtreeCommitPhaseTwo (bCleanup=1, p=0x14bbe8)
at sqlite3.c:51636
#8 sqlite3BtreeCommitPhaseTwo (p=0x14bbe8, bCleanup=1) at sqlite3.c:51622
#9 0x0008bc38 in vdbeCommit (p=0x132040, db=0x140ea8) at sqlite3.c:60636
#10 sqlite3VdbeHalt (p=0x132040) at sqlite3.c:60877
#11 0x000b8a94 in sqlite3VdbeExec (p=0x132040) at sqlite3.c:66956
#12 0x000a50b8 in sqlite3Step (p=0x132040) at sqlite3.c:62344
#13 sqlite3_step (pStmt=optimized out) at sqlite3.c:62418
#14 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#15 0x0003bde0 in DbObjCmd (cd=0x14b2e8, interp=0x107198,
objc=optimized out, objv=0x10802c) at ./src/tclsqlite.c:2251
---Type return to continue, or q return to quit---
#16 0x2aaf4348 in ?? ()
#17 0x2aaf4348 in ?? ()
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67661.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
Below is the code path just before the error below is given out / getting
printed
Expected: [0 ok]
Got: [1 {nfail=1 rc=1 result=disk I/O error}]
Breakpoint 1, ts_ftruncate (fd=5, n=206456) at ./src/test_syscall.c:272
272 static int ts_ftruncate(int fd, off_t n){
(gdb) step
273 if( tsIsFailErrno(ftruncate) ){
(gdb) next
272 static int ts_ftruncate(int fd, off_t n){
(gdb)
273 if( tsIsFailErrno(ftruncate) ){
(gdb)
276 return orig_ftruncate(fd, n);
(gdb)
unixTruncate (nByte=0, id=0x14c478) at sqlite3.c:26365
26365pFile-lastErrno = errno;
(gdb)
26366return unixLogError(SQLITE_IOERR_TRUNCATE, ftruncate,
pFile-zPath);
(gdb)
unixTruncate (id=0x14c478, nByte=optimized out) at sqlite3.c:26383
26383 }
(gdb)
unixTruncate (id=0x1, nByte=optimized out) at sqlite3.c:26348
26348 static int unixTruncate(sqlite3_file *id, i64 nByte){
(gdb)
unixLogErrorAtLine (errcode=1546, zFunc=0xc8920 ftruncate,
zPath=0x14c4e8 /home/brijesh/mySQLtry/test.db-journal, iLine=26366)
at sqlite3.c:23979
23979 ){
(gdb)
23981 int iErrno = errno; /* Saved syscall error number */
(gdb)
24017 assert( errcode!=SQLITE_OK );
(gdb)
23981 int iErrno = errno; /* Saved syscall error number */
(gdb)
24017 assert( errcode!=SQLITE_OK );
(gdb)
24018 if( zPath==0 ) zPath = ;
(gdb)
24019 sqlite3_log(errcode,
(gdb)
24018 if( zPath==0 ) zPath = ;
(gdb)
24019 sqlite3_log(errcode,
(gdb)
24025 }
(gdb)
pager_end_transaction (pPager=0x14c2e0, hasMaster=optimized out,
bCommit=1)
at sqlite3.c:39301
39301 pPager-journalOff = 0;
(gdb)
39331 sqlite3BitvecDestroy(pPager-pInJournal);
(gdb)
39332 pPager-pInJournal = 0;
(gdb)
39334 sqlite3PcacheCleanAll(pPager-pPCache);
(gdb)
39332 pPager-pInJournal = 0;
(gdb)
39333 pPager-nRec = 0;
(gdb)
39334 sqlite3PcacheCleanAll(pPager-pPCache);
(gdb)
39335 sqlite3PcacheTruncate(pPager-pPCache, pPager-dbSize);
(gdb)
39337 if( pagerUseWal(pPager) ){
(gdb)
39344 }else if( rc==SQLITE_OK bCommit
pPager-dbFileSizepPager-dbSize ){
(gdb)
39355 if( !pPager-exclusiveMode
(gdb)
39356(!pagerUseWal(pPager) || sqlite3WalExclusiveMode(pPager-pWal,
0))
(gdb)
39358rc2 = pagerUnlockDb(pPager, SHARED_LOCK);
(gdb)
39359pPager-changeCountDone = 0;
(gdb)
39364 return (rc==SQLITE_OK?rc2:rc);
(gdb)
39361 pPager-eState = PAGER_READER;
(gdb)
39364 return (rc==SQLITE_OK?rc2:rc);
(gdb)
39361 pPager-eState = PAGER_READER;
(gdb)
39362 pPager-setMaster = 0;
(gdb)
39365 }
(gdb)
sqlite3PagerCommitPhaseTwo (pPager=0x14c2e0) at sqlite3.c:43389
43389 return pager_error(pPager, rc);
(gdb)
43390 }
(gdb)
sqlite3PagerCommitPhaseTwo (pPager=0x1424c8) at sqlite3.c:43389
43389 return pager_error(pPager, rc);
(gdb)
pager_error (pPager=0x14c2e0, rc=1546) at sqlite3.c:39190
39190 assert( rc==SQLITE_OK || !MEMDB );
(gdb)
39188 static int pager_error(Pager *pPager, int rc){
(gdb)
39190 assert( rc==SQLITE_OK || !MEMDB );
(gdb)
39191 assert(
(gdb)
39189 int rc2 = rc 0xff;
(gdb)
39196 if( rc2==SQLITE_FULL || rc2==SQLITE_IOERR ){
(gdb)
39198pPager-eState = PAGER_ERROR;
(gdb)
39197pPager-errCode = rc;
(gdb)
39198pPager-eState = PAGER_ERROR;
(gdb)
39201 }
(gdb)
sqlite3BtreeCommitPhaseTwo (bCleanup=0, p=0x1424c8) at sqlite3.c:51637
51637if( rc!=SQLITE_OK bCleanup==0 ){
(gdb)
51641pBt-inTransaction = TRANS_READ;
(gdb)
51637if( rc!=SQLITE_OK bCleanup==0 ){
(gdb)
51645 sqlite3BtreeLeave(p);
(gdb)
sqlite3BtreeCommitPhaseTwo (p=0x1424c8, bCleanup=0) at sqlite3.c:51647
51647 }
(gdb)
vdbeCommit (p=0x130688, db=0x140ea8) at sqlite3.c:60485
60485for(i=0; rc==SQLITE_OK idb-nDb; i++){
(gdb)
60633for(i=0; idb-nDb; i++){
(gdb)
sqlite3VdbeHalt (p=0x130688) at sqlite3.c:60879
60879if( rc==SQLITE_BUSY p-readOnly ){
(gdb)
60882}else if( rc!=SQLITE_OK ){
(gdb)
60883 p-rc = rc;
(gdb)
60884 sqlite3RollbackAll(db, SQLITE_OK);
(gdb)
60911if( eStatementOp ){
(gdb)
60892 db-nStatement = 0;
(gdb)
60911if( eStatementOp ){
(gdb)
60928if( p-changeCntOn ){
(gdb)
60929 if( eStatementOp!=SAVEPOINT_ROLLBACK ){
(gdb)
60930sqlite3VdbeSetChanges(db, p-nChange);
(gdb)
60932sqlite3VdbeSetChanges(db, 0);
(gdb)
60934 p-nChange = 0;
60938sqlite3VdbeLeave(p);
(gdb)
60942 if( p-pc=0 ){
(gdb)
60943db-activeVdbeCnt--;
(gdb)
60942 if( p-pc=0 ){
(gdb)
60943db-activeVdbeCnt--;
(gdb)
60944if( !p-readOnly ){
(gdb)
60945 db-writeVdbeCnt--;
(gdb)
60947assert( db-activeVdbeCnt=db-writeVdbeCnt );
(gdb)
60949 p-magic = VDBE_MAGIC_HALT;
(gdb)
60950 checkActiveVdbeCnt(db);
(gdb)
60949 p-magic = VDBE_MAGIC_HALT;
(gdb)
60950 checkActiveVdbeCnt(db);
(gdb)
60951 if( p-db-mallocFailed ){
(gdb)
60952p-rc = SQLITE_NOMEM;
(gdb)
60963 assert( db-activeVdbeCnt0 || db-autoCommit==0 || db-nStatement==0
);
(gdb)
60964
Re: [sqlite] TCL Test failures on ARM
i tried putting break point at robust_ftruncate() but it was not successful (gdb) break robust_ftruncate Function robust_ftruncate not defined. the symbol table of testfixture was not having this i believe. does it have anything to do with crosscompiling ? below are the commands i used for cross compile LDFLAGS=-L/home/philips/bk_tcl/usr/local/lib CC=armv7l-timesys-linux-gnueabi-gcc ./configure --host=armv7l-timesys-linux-gnueabi --enable-shared TARGET_READLINE_INC= --with-tcl=/home/philips/bk_tcl/usr/local/lib make make test Thank you Brijesh -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67664.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
i tried putting break point at robust_ftruncate() but it was not successful (gdb) break robust_ftruncate Function robust_ftruncate not defined. the symbol table of testfixture was not having robust_ftruncate when i read the testfixture(attached). does it have anything to do with crosscompiling ? below are the commands i used for cross compile elfread http://sqlite.1065341.n5.nabble.com/file/n67667/elfread LDFLAGS=-L/home/philips/bk_tcl/usr/local/lib CC=armv7l-timesys-linux-gnueabi-gcc ./configure --host=armv7l-timesys-linux-gnueabi --enable-shared TARGET_READLINE_INC= --with-tcl=/home/philips/bk_tcl/usr/local/lib make make test Thank you Brijesh -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67667.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
Any one knows how to fix it ? -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67621.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
Has anyone came across same problem ? Appreciate if someone can point out what’s going wrong with these tests -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67637.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] TCL Test failures on ARM
Hi,
When i executed the TCL: tests on my ARM board (nitrogen 6X) the below tests
are
failing with the message
Expected: [0 ok]
Got: [1 {nfail=1 rc=1 result=disk I/O error}]
sysfault-2.1-vfsfault-transient
memsubsys1.sysfault-2.1-vfsfault-transient
memsubsys2.sysfault-2.1-vfsfault-transient
no_mutex_try.sysfault-2.1-vfsfault-transient
journaltest.sysfault-2.1-vfsfault-transient
inmemory_journal.sysfault-2.1-vfsfault-transient
What could be the reason for these failures? and how can i proceed further
with this ?
Thank You
Brijesh
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] TCL Test failures on ARM
yes there were 142 in each of those tests, that is, transient.1... to transient.142... in each of the sets i mentioned above -- View this message in context: http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67614.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] cross compiling sqlite
HI, Thank you for the reply. i have cross-compiled tcl and sqlite for ARM , but i am facing some result=disk I/O error issue which i have posted as a new thread . Thank you Brijesh -- View this message in context: http://sqlite.1065341.n5.nabble.com/cross-compiling-sqlite-tp67478p67615.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] cross compiling sqlite
any one tried to run sqlite test suite on arm target ? -- View this message in context: http://sqlite.1065341.n5.nabble.com/cross-compiling-sqlite-tp67478p67513.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] cross compiling sqlite
How to create testfixture that could run on arm ? -- View this message in context: http://sqlite.1065341.n5.nabble.com/cross-compiling-sqlite-tp67478p67515.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] cross compiling sqlite
Hi i have crosscompiled selite for arm board by below command from my ubuntu machine 1. ./configure --host=arm CC=armv7l-timesys-linux-gnueabi-gcc --disable-tcl 2. make 3. make install DESTDIR=/usr/bk and later put the contents from bk to the target also i copied the source tree to target. Can any one tel me , How to run the sqlite test suite on the target ? Thank you -- View this message in context: http://sqlite.1065341.n5.nabble.com/cross-compiling-sqlite-tp67478.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] malloc failures on ubuntu
but i have got 142 errors out of 2083931 tests (result of alltest excution) but you told its 119415 , so is it doing any thing more ? Brijesh -- View this message in context: http://sqlite.1065341.n5.nabble.com/malloc-failures-on-ubuntu-tp65936p66148.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] malloc failures on ubuntu
but i have got 142 errors out of 2083931 tests (result of alltest excution) but you told its 119415 , so is it doing any thing more ? Brijesh -- View this message in context: http://sqlite.1065341.n5.nabble.com/malloc-failures-on-ubuntu-tp65936p66149.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] malloc failures on ubuntu
Below are the steps i followed in my Ubuntu PC: 1. From the site : http://www.sqlite.org/download.html 2. connected to http://www.sqlite.org/cgi/src (Dallas) 3. clicked [52e755943f] Leaf ( which was on the top) 4. clicked ZIP archive 5. saved the file 6. copied the zip file(SQLite-52e755943f87354f.zip) and extracted 7. in the terminal navigated to the extracted directory 8. Commanded for ./configure and then maketest Please correct, if something am doing wrong here. -- View this message in context: http://sqlite.1065341.n5.nabble.com/malloc-failures-on-ubuntu-tp65936p66136.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] malloc failures on ubuntu
Really appritiate if any one can help me on this, I didnot get a solution for this Thanks Brijesh -- View this message in context: http://sqlite.1065341.n5.nabble.com/malloc-failures-on-ubuntu-tp65936p66126.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
