Re: [sqlite] TCL Test failures on ARM

[Bk]

Hi,

Thank you all for the reply.

i am still wondering why setting DSQLITE_DISABLE_LFS=1 had no effect on the
code when we have a clear #ifndef ? , 

1) if my application does not need LFS , how do i really make it here
(system uses : Linux nitrogen6x 3.0.15-ts-armv7l) ?

i was getting sizeof(off_t) to 8 in robust_ftruncate and 4 in ts_ftruncate

i was expecting DSQLITE_DISABLE_LFS=1 should make  sizeof(off_t) to 4 in
robust_ftruncate , but it didnt.

solution tried: 

2) Later i added below code in the begining of test_syscall.c which made
ts_ftruncate() 's  sizeof(off_t)  to change to 8. 

#ifndef SQLITE_DISABLE_LFS
# define _LARGE_FILE   1
# ifndef _FILE_OFFSET_BITS
#   define _FILE_OFFSET_BITS 64
# endif
# define _LARGEFILE_SOURCE 1
#endif

3) Another solution i tried was setting -D_FILE_OFFSET_BITS=64 while
building 





--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67995.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

[Simon Slavin]

On 2 Apr 2013, at 8:33am, Bk  wrote:

> 1) i am using Linux 32bit on the embedded device,  is it okey to give
> "-D_FILE_OFFSET_BITS=64 " ?

Yep.  Theoretically it may be a little slower or lack backward compatibility, 
but if it compiles at all, it should be fine.  The other way around would be 
bad but that way is okay as long as your whole app uses it.

> 2) what is the significance of -D_FILE_OFFSET_BITS=64" ?

Standard file library sees this setting and knows to use the 64-bit variants of 
file operation functions and types.  For instance, if you refer to 'off_t' in 
your code, it will be understood as 'off64_t'.

You might instead want to look into _LARGEFILE64_SOURCE .  I have no idea 
whether this does actually make a difference to SQLite, though.

Warning: all of this is getting into territory where deep understanding of your 
compiler is useful.  If you never intended to get this detailed, you may be 
going up the wrong avenue.

Simon.
___
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

[Bk]

Hi,

i have noticed that the tests pass if built with below command

TCC = armv7l-timesys-linux-gnueabi-gcc   -D_FILE_OFFSET_BITS=64 
-DSQLITE_OS_UNIX=1 -I. -I${TOP}/src -I${TOP}/ext/rtree

Where i have added "-D_FILE_OFFSET_BITS=64" . 

1) i am using Linux 32bit on the embedded device,  is it okey to give
"-D_FILE_OFFSET_BITS=64 " ? 

2) what is the significance of -D_FILE_OFFSET_BITS=64" ?


Thank You




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67991.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

[Dan Kennedy]

On 04/01/2013 01:15 PM, Bk wrote:

I have updated make file with "TCC = armv7l-timesys-linux-gnueabi-gcc   -g
-DSQLITE_OS_UNIX=1 -DSQLITE_DISABLE_LFS=1 -I. -I${TOP}/src
-I${TOP}/ext/rtree"


The test still fails with DSQLITE_DISABLE_LFS=1 with same error

sysfault-2.setup... Ok
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
sysfault-2.1-vfsfault-transient.1...
Expected: [0 ok]
  Got: [1 {nfail=1 rc=1 result=disk I/O error}]


Below is the debugger screen with value of "sizeof(off_t)" . The values
seems different 4 in ts_ftruncate and 8 in robust_ftruncate.


That'll be the reason the test is failing. For whatever reason the
test_syscall.c file is being compiled with a different definition
of off_t  (and probably other stuff) than os_unix.c. Find out why
and you'll know how to fix the test.

It will be (I imagine) something to do with the pre-processor magic
at the top of os_unix.c. Perhaps something included there that isn't
included in test_syscall.c

I would have thought it would be the SQLITE_DISABLE_LFS though. You
did a clean build with the new Makefile?

Dan.


___
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

[Michael Black]

What's the ulimit for file sizes on your system?  You might be hitting that.


-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Bk
Sent: Monday, April 01, 2013 1:16 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] TCL Test failures on ARM

I have updated make file with "TCC = armv7l-timesys-linux-gnueabi-gcc   -g
-DSQLITE_OS_UNIX=1 -DSQLITE_DISABLE_LFS=1 -I. -I${TOP}/src
-I${TOP}/ext/rtree"


The test still fails with DSQLITE_DISABLE_LFS=1 with same error

sysfault-2.setup... Ok
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
sysfault-2.1-vfsfault-transient.1...
Expected: [0 ok]
 Got: [1 {nfail=1 rc=1 result=disk I/O error}]


Below is the debugger screen with value of "sizeof(off_t)" . The values
seems different 4 in ts_ftruncate and 8 in robust_ftruncate. I hope this is
what you asked me to check 

(gdb) break ts_ftruncate
Cannot access memory at address 0x0
Breakpoint 1 at 0x455e0: file ./src/test_syscall.c, line 273.
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=5, n=284108) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) p sizeof(off_t)
$1 = 4
(gdb) break robust_ftruncate
Breakpoint 2 at 0x6371c: file sqlite3.c, line 23440.
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23440
23440 rc = osFtruncate(h,sz);
(gdb) p sizeof(off_t)
$2 = 8
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=7, n=284108) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) p sizeof(off_t)
$3 = 4
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=8, sz=0) at sqlite3.c:23440
23440 rc = osFtruncate(h,sz);
(gdb) p sizeof(off_t)
$4 = 8
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=8, n=284108) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) p sizeof(off_t)
$5 = 4
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23440
23440 rc = osFtruncate(h,sz);
(gdb) p sizeof(off_t)
$6 = 8
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=7, n=284108) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) p sizeof(off_t)
$7 = 4
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=5, sz=24576) at sqlite3.c:23440
23440 rc = osFtruncate(h,sz);
(gdb) p sizeof(off_t)
$8 = 8
(gdb) 




--
View this message in context:
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67984.h
tml
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-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] TCL Test failures on ARM

[Bk]

I have updated make file with "TCC = armv7l-timesys-linux-gnueabi-gcc   -g
-DSQLITE_OS_UNIX=1 -DSQLITE_DISABLE_LFS=1 -I. -I${TOP}/src
-I${TOP}/ext/rtree"


The test still fails with DSQLITE_DISABLE_LFS=1 with same error

sysfault-2.setup... Ok
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
sysfault-2.1-vfsfault-transient.1...
Expected: [0 ok]
 Got: [1 {nfail=1 rc=1 result=disk I/O error}]


Below is the debugger screen with value of "sizeof(off_t)" . The values
seems different 4 in ts_ftruncate and 8 in robust_ftruncate. I hope this is
what you asked me to check 

(gdb) break ts_ftruncate
Cannot access memory at address 0x0
Breakpoint 1 at 0x455e0: file ./src/test_syscall.c, line 273.
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=5, n=284108) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) p sizeof(off_t)
$1 = 4
(gdb) break robust_ftruncate
Breakpoint 2 at 0x6371c: file sqlite3.c, line 23440.
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23440
23440 rc = osFtruncate(h,sz);
(gdb) p sizeof(off_t)
$2 = 8
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=7, n=284108) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) p sizeof(off_t)
$3 = 4
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=8, sz=0) at sqlite3.c:23440
23440 rc = osFtruncate(h,sz);
(gdb) p sizeof(off_t)
$4 = 8
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=8, n=284108) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) p sizeof(off_t)
$5 = 4
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23440
23440 rc = osFtruncate(h,sz);
(gdb) p sizeof(off_t)
$6 = 8
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=7, n=284108) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) p sizeof(off_t)
$7 = 4
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=5, sz=24576) at sqlite3.c:23440
23440 rc = osFtruncate(h,sz);
(gdb) p sizeof(off_t)
$8 = 8
(gdb) 




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67984.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

[Dan Kennedy]

On 03/29/2013 04:35 PM, Bk wrote:

The perror("ftruncate") is printing ftruncate: : File too large . i have a
2GB card in the embedded device with 50% mem free.


Seems like EFBIG. What value is actually being passed
as the second argument to the system ftruncate() call?

Does the test pass if you build with -DSQLITE_DISABLE_LFS?

In the debugger, does the expression "sizeof(off_t)" evaluate
to the same value in the ts_ftruncate() frame as it does
in robust_ftruncate()?






Below is the output window shows when the test executed.


sysfault-2.setup... Ok
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
sysfault-2.1-vfsfault-transient.1...
Expected: [0 ok]
  Got: [1 {nfail=1 rc=1 result=disk I/O error}]

Below is the backtrace when the failure is printed (the expected - Got
message)

(gdb) backtrace
#0  robust_ftruncate (h=5, sz=24576) at sqlite3.c:23440
#1  0x00065a1c in fcntlSizeHint (pFile=0x16fcb8, nByte=22528)
 at sqlite3.c:26305
#2  0x00065d04 in unixFileControl (id=0x16fcb8, op=5, pArg=0x7effed80)
 at sqlite3.c:26359
#3  0x00059560 in sqlite3OsFileControlHint (id=0x16fcb8, op=5,
pArg=0x7effed80)
 at sqlite3.c:14920
#4  0x000702b4 in pager_write_pagelist (pPager=0x16fbc0, pList=0x181ffc)
 at sqlite3.c:41001
#5  0x00072878 in sqlite3PagerCommitPhaseOne (pPager=0x16fbc0,
 zMaster=0x1b5a18 "/home/brijesh/SQLite-3.7.14.1/test.db-mjED751E9E4",
 noSync=0) at sqlite3.c:42879
#6  0x0007de8c in sqlite3BtreeCommitPhaseOne (p=0x16f718,
 zMaster=0x1b5a18 "/home/brijesh/SQLite-3.7.14.1/test.db-mjED751E9E4")
 at sqlite3.c:51071
#7  0x0008e90c in vdbeCommit (db=0x16b360, p=0x1be590) at sqlite3.c:60059
#8  0x0008ef04 in sqlite3VdbeHalt (p=0x1be590) at sqlite3.c:60333
#9  0x00098168 in sqlite3VdbeExec (p=0x1be590) at sqlite3.c:66334
#10 0x000918b8 in sqlite3Step (p=0x1be590) at sqlite3.c:61775
#11 0x00091ad4 in sqlite3_step (pStmt=0x1be590) at sqlite3.c:61848
#12 0x0004fdd4 in dbEvalStep (p=0x7efff170) at ./src/tclsqlite.c:1400
#13 0x00051b38 in DbObjCmd (cd=0x14a470, interp=0x122f80, objc=3,
 objv=0x12a764) at ./src/tclsqlite.c:2251




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67959.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-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] TCL Test failures on ARM

[Bk]

The perror("ftruncate") is printing ftruncate: : File too large . i have a
2GB card in the embedded device with 50% mem free. 

Below is the output window shows when the test executed.


sysfault-2.setup... Ok
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
ftruncate: : File too large
sysfault-2.1-vfsfault-transient.1...
Expected: [0 ok]
 Got: [1 {nfail=1 rc=1 result=disk I/O error}]

Below is the backtrace when the failure is printed (the expected - Got
message)

(gdb) backtrace
#0  robust_ftruncate (h=5, sz=24576) at sqlite3.c:23440
#1  0x00065a1c in fcntlSizeHint (pFile=0x16fcb8, nByte=22528)
at sqlite3.c:26305
#2  0x00065d04 in unixFileControl (id=0x16fcb8, op=5, pArg=0x7effed80)
at sqlite3.c:26359
#3  0x00059560 in sqlite3OsFileControlHint (id=0x16fcb8, op=5,
pArg=0x7effed80)
at sqlite3.c:14920
#4  0x000702b4 in pager_write_pagelist (pPager=0x16fbc0, pList=0x181ffc)
at sqlite3.c:41001
#5  0x00072878 in sqlite3PagerCommitPhaseOne (pPager=0x16fbc0, 
zMaster=0x1b5a18 "/home/brijesh/SQLite-3.7.14.1/test.db-mjED751E9E4", 
noSync=0) at sqlite3.c:42879
#6  0x0007de8c in sqlite3BtreeCommitPhaseOne (p=0x16f718, 
zMaster=0x1b5a18 "/home/brijesh/SQLite-3.7.14.1/test.db-mjED751E9E4")
at sqlite3.c:51071
#7  0x0008e90c in vdbeCommit (db=0x16b360, p=0x1be590) at sqlite3.c:60059
#8  0x0008ef04 in sqlite3VdbeHalt (p=0x1be590) at sqlite3.c:60333
#9  0x00098168 in sqlite3VdbeExec (p=0x1be590) at sqlite3.c:66334
#10 0x000918b8 in sqlite3Step (p=0x1be590) at sqlite3.c:61775
#11 0x00091ad4 in sqlite3_step (pStmt=0x1be590) at sqlite3.c:61848
#12 0x0004fdd4 in dbEvalStep (p=0x7efff170) at ./src/tclsqlite.c:1400
#13 0x00051b38 in DbObjCmd (cd=0x14a470, interp=0x122f80, objc=3, 
objv=0x12a764) at ./src/tclsqlite.c:2251




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67959.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

[Dan Kennedy]

On 03/28/2013 02:18 PM, Bk wrote:

Hi,

The osFtruncate is not returning zero value.


And what is it setting errno to? At line 23440, when rc is non-zero,
what does perror("ftruncate") print?

Dan.






i have put breakpoint at

ts_ftruncate abd robust_ftruncate


(gdb) break robust_ftruncate
Breakpoint 2 at 0x636ec: file sqlite3.c, line 23439.
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23439
23439  do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR );
(gdb) p rc
$1 = 1
(gdb) step

Breakpoint 1, ts_ftruncate (fd=7, n=284060) at ./src/test_syscall.c:273
273  if( tsIsFailErrno("ftruncate") ){
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=8, sz=0) at sqlite3.c:23439
23439  do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR );
(gdb) p rc
$2 = 449088
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=8, n=284060) at ./src/test_syscall.c:273
273  if( tsIsFailErrno("ftruncate") ){
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23439
23439  do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR );
(gdb) p rc
$3 = 365128
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=7, n=284060) at ./src/test_syscall.c:273
273  if( tsIsFailErrno("ftruncate") ){
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=5, sz=24576) at sqlite3.c:23439
23439  do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR );
(gdb)




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67936.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-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] TCL Test failures on ARM

[Bk]

Hi, 

The osFtruncate is not returning zero value. i have put breakpoint at
ts_ftruncate abd robust_ftruncate 


(gdb) break robust_ftruncate 
Breakpoint 2 at 0x636ec: file sqlite3.c, line 23439. 
(gdb) continue 
Continuing. 

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23439 
23439  do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR ); 
(gdb) p rc 
$1 = 1 
(gdb) step 

Breakpoint 1, ts_ftruncate (fd=7, n=284060) at ./src/test_syscall.c:273 
273  if( tsIsFailErrno("ftruncate") ){ 
(gdb) continue 
Continuing. 

Breakpoint 2, robust_ftruncate (h=8, sz=0) at sqlite3.c:23439 
23439  do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR ); 
(gdb) p rc 
$2 = 449088 
(gdb) continue 
Continuing. 

Breakpoint 1, ts_ftruncate (fd=8, n=284060) at ./src/test_syscall.c:273 
273  if( tsIsFailErrno("ftruncate") ){ 
(gdb) continue 
Continuing. 

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23439 
23439  do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR ); 
(gdb) p rc 
$3 = 365128 
(gdb) continue 
Continuing. 

Breakpoint 1, ts_ftruncate (fd=7, n=284060) at ./src/test_syscall.c:273 
273  if( tsIsFailErrno("ftruncate") ){ 
(gdb) continue 
Continuing. 

Breakpoint 2, robust_ftruncate (h=5, sz=24576) at sqlite3.c:23439 
23439  do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR ); 
(gdb) 




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67936.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

[Bk]

Hi, 

The osFtruncate is not returning non zero value. i have put breakpoint at
ts_ftruncate abd robust_ftruncate


(gdb) break robust_ftruncate
Breakpoint 2 at 0x636ec: file sqlite3.c, line 23439.
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23439
23439 do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR );
(gdb) p rc
$1 = 1
(gdb) step

Breakpoint 1, ts_ftruncate (fd=7, n=284060) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=8, sz=0) at sqlite3.c:23439
23439 do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR );
(gdb) p rc
$2 = 449088
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=8, n=284060) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=7, sz=0) at sqlite3.c:23439
23439 do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR );
(gdb) p rc
$3 = 365128
(gdb) continue
Continuing.

Breakpoint 1, ts_ftruncate (fd=7, n=284060) at ./src/test_syscall.c:273
273   if( tsIsFailErrno("ftruncate") ){
(gdb) continue
Continuing.

Breakpoint 2, robust_ftruncate (h=5, sz=24576) at sqlite3.c:23439
23439 do{ rc = osFtruncate(h,sz); }while( rc<0 && errno==EINTR );
(gdb) 




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67935.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

[Drake Wilson]

Quoth Bk , on 2013-03-17 21:25:21 -0700:
> can some one point out what went wrong here ?

Community lists do not provide guaranteed responses, and repeatedly
hassling the list with requests for one is unlikely to make you any
friends.  Certainly I haven't responded because I don't have easy
access to an ARM configuration with which to reproduce this.  I would
guess many others on the list are in a similar situation.

You've now sent _seven_ messages in this thread with no content other
than "someone talk to me".  This is not polite.

If you are in need of a guaranteed response, may I suggest hiring
someone to be specifically responsible for giving you the results you
need?  http://www.hwaci.com/sw/sqlite/prosupport.html is an obvious
place to start.

   ---> Drake Wilson
___
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

[Bk]

can some one point out what went wrong here ?



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67741.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

[Bk]

Hi,


can any one tel me how can i fix this issue ?



Thank you

Brijesh



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TCL-Test-failures-on-ARM-tp67612p67727.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

[bkk]

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

[Dan Kennedy]

On 03/13/2013 01:03 PM, bkk wrote:

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( rc<0 && errno==EINTR );


The test was supposed to inject an error into osFtruncate() so
that the first time it is called it returns a non-zero value
and sets errno to EINTR. Then the second time to return zero
(success). What is actually happening?

Dan.



___
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

[bkk]

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

[bkk]

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( rc<0 && 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  to continue, or q  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

[bkk]

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

[bkk]

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

[bkk]

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( rc<0 && 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->dbFileSize>pPager->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; inDb; 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 (rc>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 =

Re: [sqlite] TCL Test failures on ARM

[bkk]

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
  

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

[Dan Kennedy]

On 03/13/2013 11:52 AM, bkk wrote:

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 ?


Probably just optimized out. After running the configure command try
editing the Makefile and removing "-O2" from the "TCC = " line. Or
any other -O switches that are there.

Or you might just be able to add "CFLAGS=-g" to the command line.

Dan.





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



___
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

[bkk]

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

[bkk]

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=) at sqlite3.c:26383 
26383 } 
(gdb) 
unixTruncate (id=0x1, nByte=) 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=,
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->dbFileSize>pPager->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 && inDb; i++){ 
(gdb) 
60633for(i=0; inDb; 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->activeVdbeCnt>0 || db->autoCommit==0 || 

Re: [sqlite] TCL Test failures on ARM

[bkk]

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=) at sqlite3.c:26348
#4  0x00069284 in sqlite3OsTruncate (size=0, id=0x150b60) at sqlite3.c:15034
#5  pager_end_transaction (pPager=0x1509c8, hasMaster=, 
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=) at sqlite3.c:62418
#14 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#15 0x0003bde0 in DbObjCmd (cd=0x14b2e8, interp=0x107198, 
objc=, objv=0x10802c) at ./src/tclsqlite.c:2251
---Type  to continue, or q  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

[bkk]

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=) at sqlite3.c:26383
26383   }
(gdb) 
unixTruncate (id=0x1, nByte=) 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=,
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->dbFileSize>pPager->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; inDb; i++){ 
(gdb) 
60634 Btree *pBt = db->aDb[i].pBt;
(gdb) 
60635 if( pBt ){
(gdb) 
60633   for(i=0; inDb; 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

[Dan Kennedy]

On 03/12/2013 06:45 PM, bkk wrote:

Below is the backtrace from the gdb when the failure happened.


Seems odd to me. Assuming this is happening within the sysfault-2.1
test case, then the first stack should be setting errno to EINTR.
Causing the robust_ftruncate() function to retry ts_ftruncate().
The second call should succeed.

Is it invoking ts_ftruncate() a second time after the first (failing)
call returns. Is the failing call that we can see in the stack trace
below really setting errno to EINTR?

Dan.





#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=) at sqlite3.c:26348
#6  0x00069284 in sqlite3OsTruncate (size=0, id=0x12f2e0) at sqlite3.c:15034
#7  pager_end_transaction (pPager=0x12f148, hasMaster=,
 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=) at sqlite3.c:62418
#16 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#17 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198,
 objc=, objv=0x10802c) at ./src/tclsqlite.c:2251

(gdb) backtrace
#0  unixTruncate (nByte=0, id=0x12f2e0) at sqlite3.c:26366
#1  unixTruncate (id=0x12f2e0, nByte=) at sqlite3.c:26348
#2  0x00069284 in sqlite3OsTruncate (size=0, id=0x12f2e0) at sqlite3.c:15034
#3  pager_end_transaction (pPager=0x12f148, hasMaster=,
 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=) at sqlite3.c:62418
#12 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#13 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198,
 objc=, 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=,
 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=) at sqlite3.c:62418
#11 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#12 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198,
 objc=, objv=0x10802c) at ./src/tclsqlite.c:2251
#13 0x2aaf4348 in ?? ()
#14 0x2aaf4348 in ?? ()

#0  sqlite3Step (p=) at sqlite3.c:62366
#1  sqlite3_step (pStmt=) at sqlite3.c:62418
#2  0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#3  0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198,
 objc=, 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



___
sqlite-users 

Re: [sqlite] TCL Test failures on ARM

[bkk]

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=) at sqlite3.c:26348
#6  0x00069284 in sqlite3OsTruncate (size=0, id=0x12f2e0) at sqlite3.c:15034
#7  pager_end_transaction (pPager=0x12f148, hasMaster=, 
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=) at sqlite3.c:62418
#16 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#17 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198, 
objc=, objv=0x10802c) at ./src/tclsqlite.c:2251

(gdb) backtrace
#0  unixTruncate (nByte=0, id=0x12f2e0) at sqlite3.c:26366
#1  unixTruncate (id=0x12f2e0, nByte=) at sqlite3.c:26348
#2  0x00069284 in sqlite3OsTruncate (size=0, id=0x12f2e0) at sqlite3.c:15034
#3  pager_end_transaction (pPager=0x12f148, hasMaster=, 
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=) at sqlite3.c:62418
#12 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#13 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198, 
objc=, 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=, 
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=) at sqlite3.c:62418
#11 0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#12 0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198, 
objc=, objv=0x10802c) at ./src/tclsqlite.c:2251
#13 0x2aaf4348 in ?? ()
#14 0x2aaf4348 in ?? ()

#0  sqlite3Step (p=) at sqlite3.c:62366
#1  sqlite3_step (pStmt=) at sqlite3.c:62418
#2  0x00038a78 in dbEvalStep (p=0x7efff288) at ./src/tclsqlite.c:1400
#3  0x0003bde0 in DbObjCmd (cd=0x130468, interp=0x107198, 
objc=, 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

[Dan Kennedy]

On 03/12/2013 10:48 AM, bkk wrote:

Has anyone came across same problem ? Appreciate if someone can point out
what’s going wrong with these tests


Is there something odd about trying to write to errno on this
platform? These tests depend on function tsIsFailErrno() in
file test_syscall.c being able to assign a value to errno.

Are you able to check with a debugger (or otherwise) if that
is actually working?

Dan.


___
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

[bkk]

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

Re: [sqlite] TCL Test failures on ARM

[bkk]

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

[bkk]

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] TCL Test failures on ARM

[Dan Kennedy]

On 03/11/2013 10:52 AM, bkk wrote:

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 ?


The tests inject errors into various system calls (open, ftruncate,
close, read - you can see the list in the test file). The errors are
injected such that they set errno to EINTR. In this case SQLite is
supposed to retry the system call. But in your case it looks like it
is returning an error to the user instead.

Are the test case names above truncated? Do you mean that all tests
that match the pattern "sysfault-2.1-vfsfault-transient*" etc. failed?

Dan.


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] TCL Test failures on ARM

[bkk]

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