1. 31 Aug, 2015 1 commit
  2. 28 Aug, 2015 1 commit
  3. 12 Jun, 2015 2 commits
  4. 11 Jun, 2015 2 commits
  5. 09 May, 2015 1 commit
  6. 08 May, 2015 1 commit
    • Nick Kralevich's avatar
      sqlite: upgrade to SQLite 3.8.10 · 3d169392
      Nick Kralevich authored
      Downloaded from https://www.sqlite.org/2015/sqlite-amalgamation-3081000.zip
      
        $ sha256sum sqlite-amalgamation-3081000.zip
        b864bf802584e54a881db4ab9c8fb54b51339b2dc2c66f97fbf88ae4ee052ff8  sqlite-amalgamation-3081000.zip
      
      dist/orig contains the stock sqlite3 code, as packaged in the ZIP file above.
      
      dist contains a copy of dist/orig, but with the Android.patch file applied.
      Please see Android.patch for a list of differences between stock and
      Android.
      
      One Android patch failed to apply cleanly, due to a change in how one
      variable is handled. The patch was fixed. Other than that, no changes
      to the Android specific patches.
      
      Description of changes compared to SQLite 3.8.9:
      
        SQLite Release 3.8.10 On 2015-05-07
      
        Added the sqldiff.exe utility program for computing the differences between two SQLite database files.
        Added the y format string to the matchinfo() function of FTS3.
        Performance improvements for ORDER BY, VACUUM, CREATE INDEX, PRAGMA integrity_check, and PRAGMA quick_check.
        Fix many obscure problems discovered while SQL fuzzing.
        Identify all methods for important objects in the interface documentation. (example)
        Made the American Fuzzy Lop fuzzer a standard part of SQLite's testing strategy.
        Add the ".binary" and ".limits" commands to the command-line shell.
        Make the "dbstat" virtual table part of standard builds when compiled with the SQLITE_ENABLE_DBSTAT_VTAB option.
        SQLITE_SOURCE_ID: "2015-05-07 11:53:08 cf975957b9ae671f34bb65f049acf351e650d437"
        SHA1 for sqlite3.c: 0b34f0de356a3f21b9dfc761f3b7821b6353c570
      
      Change-Id: I9d298922ddf405a597781749c8b39caee4ea638b
      3d169392
  7. 08 Apr, 2015 2 commits
  8. 15 Jan, 2015 4 commits
  9. 14 Jan, 2015 1 commit
  10. 05 Jan, 2015 3 commits
  11. 19 Nov, 2014 4 commits
    • Martin Storsjo's avatar
      am 006c7975: Store inodes in unsigned long long · 6fbaf20e
      Martin Storsjo authored
      * commit '006c7975':
        Store inodes in unsigned long long
      6fbaf20e
    • Narayan Kamath's avatar
      a561e9ca
    • Martin Storsjo's avatar
      Store inodes in unsigned long long · 006c7975
      Martin Storsjo authored
      In 32 bit ABIs, ino_t is a 32 bit type, while the st_ino field
      in struct stat is 64 bits wide in both 32 and 64 bit processes.
      This means that struct stat can expose inode numbers that are
      truncated when stored in an ino_t.
      
      The SDCard fuse daemon (/system/bin/sdcard) uses raw pointer
      values as inode numbers, so on 64 bit devices, we're very likely
      to observe inodes that need > 32 bits to represent.
      
      The fileHasMoved function in sqlite compares the stored
      inode value with a new one from stat, and when the stored
      value is truncated, this check will falsely indicate that
      the file has been moved. When the fileHasMoved function
      triggers, other functions start returning errors indicating
      that the database is in read-only mode.
      
      NOTE: Bionic differs from glibc in that struct stat's st_ino
      is *always* 64 bits wide, and not the same width as ino_t.
      
      bug: https://code.google.com/p/android/issues/detail?id=79994
      bug: 18434265
      
      (cherry picked from commit eef2c431)
      
      Change-Id: I832e0084e86c9a31519764d87df499ece05b488d
      006c7975
    • Martin Storsjo's avatar
      Store inodes in unsigned long long · eef2c431
      Martin Storsjo authored
      In 32 bit ABIs, ino_t is a 32 bit type, while the st_ino field
      in struct stat is 64 bits wide in both 32 and 64 bit processes.
      This means that struct stat can expose inode numbers that are
      truncated when stored in an ino_t.
      
      The SDCard fuse daemon (/system/bin/sdcard) uses raw pointer
      values as inode numbers, so on 64 bit devices, we're very likely
      to observe inodes that need > 32 bits to represent.
      
      The fileHasMoved function in sqlite compares the stored
      inode value with a new one from stat, and when the stored
      value is truncated, this check will falsely indicate that
      the file has been moved. When the fileHasMoved function
      triggers, other functions start returning errors indicating
      that the database is in read-only mode.
      
      NOTE: Bionic differs from glibc in that struct stat's st_ino
      is *always* 64 bits wide, and not the same width as ino_t.
      
      bug: https://code.google.com/p/android/issues/detail?id=79994
      bug: 18434265
      
      Change-Id: Id79a866c8891d6df47e4eec17ad9eb48e4cb0138
      eef2c431
  12. 12 Sep, 2014 2 commits
  13. 11 Sep, 2014 3 commits
  14. 10 Sep, 2014 1 commit
  15. 09 Sep, 2014 1 commit
  16. 20 Aug, 2014 1 commit
  17. 14 Jul, 2014 3 commits
  18. 10 Jul, 2014 2 commits
  19. 09 Jul, 2014 2 commits
  20. 07 Jun, 2014 3 commits