On Wed, Sep 16, 2009 at 1:07 PM, Mike Mammarella <m...@chromium.org> wrote:
> On Wed, Sep 16, 2009 at 12:59 PM, Evan Martin <e...@chromium.org> wrote:
>> On Wed, Sep 16, 2009 at 12:44 PM, spotrh <spo...@gmail.com> wrote:
>>> On 09/16/2009 02:23 PM, Evan Martin wrote:
>>>> What is the error message? I wonder if there is something
>>>> Linux-specific where we're getting an error code that is harmless.
>>>> (We've had a lot of that in code that checks errno where the value
>>>> differs between Linux and OS X.)
>>>
>>> User says it reports:
>>>
>>> [5070:5093:8302515214:FATAL:/mnt/chromium/rpmbuild/BUILD/chromium-20090910svn25958/src/chrome/common/sqlite_utils.cc(52)]
>>> Check failed: false. sqlite fatal error 11
>>
>> Hm, that doesn't sound good!
>>
>> #define SQLITE_CORRUPT 11 /* The database disk image is malformed */
>
> FYI, I'm almost finished updating our (locally patched) SQLite to
> version 3.6.18 instead of 3.6.1 that we have now; apparently 3.6.18
> handles corruption much better than 3.6.1 does. (I am holding off
> checking it in until I can run it through all the tests I can find to
> make sure something won't break, but other than that it's ready.) I
> don't know what effect it might have on this issue, but hopefully it
> will be a good effect...
To be clear, newer SQLite "handles corruption much better" in the
sense that it detects it and throws SQLITE_CORRUPT in cases which
previous code did not detect. In general, if the older code throws
SQLITE_CORRUPT, the newer code will also throw SQLITE_CORRUPT.
-scott
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
