I'm using the default allocator, and it is a uclinux system without dynamic libraries, everything must be staticaly linked, so ltrace can't help (anyway, I think there is no ltrace available for this machine).
I'll try to use gdbserver to debug it, but I really don't understand why sqlite3 is doing different things (working/not working) depending on which filesystem the database file is located. Salud, Roberto Lumbreras On Tue, Feb 10, 2009 at 9:42 PM, Roger Binns <rog...@rogerbinns.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Roberto Lumbreras wrote: > > With strace the problem is clear: sqlite3 calls "old_mmap" with length=0. > > I'm running version 2.6.25-uc0 of uCLinux, so mmap returns EINVAL because > > length==0, then sqlite3 says "out of memory". > > The default SQLite 3 code never calls mmap. Go ahead and grep the code > to see! Are you using a custom allocator? If not then your malloc > library is the problem. > > The ltrace command can help find the library routines responsible. > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkmR5psACgkQmOOfHg372QT0DACgyI1/4fN5H2jFBPELIEiRRy1c > 3HcAoMIDA7tNIW4K9SO4BVeIctQI3zjw > =ssx5 > -----END PGP SIGNATURE----- > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
