Re: [sqlite] Header corruption

, big team - you know how it goes). - Deon -Original Message- From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> On Behalf Of Olivier Mascia Sent: Tuesday, April 17, 2018 2:28 PM To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sql

Re: [sqlite] Header corruption

2018 1:54 PM To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sqlite] Header corruption On Apr 17, 2018, at 2:07 PM, Deon Brewis <de...@outlook.com> wrote: > > One just has to be in the mindset that on unix based platforms, a socket is a > fi

Re: [sqlite] Header corruption

ter Da Silva Sent: Tuesday, April 17, 2018 1:13 PM To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sqlite] Header corruption On 4/17/18, 3:08 PM, "sqlite-users on behalf of Deon Brewis" <sqlite-users-boun...@mailinglists.sqlite.org on behalf of de...@

Re: [sqlite] Header corruption

> Le 17 avr. 2018 à 22:07, Deon Brewis a écrit : > > closesocket(_socket); // posix socket > SSL_shutdown(_ssl); // openssl (_ssl was initialized using the _socket above) These two statements are inherently wrong, in this order. First you SSL_shutdown(), then you

Re: [sqlite] Header corruption

On Apr 17, 2018, at 2:07 PM, Deon Brewis wrote: > > One just has to be in the mindset that on unix based platforms, a socket is a > file handle. (Not instinctive if you're coming from a Windows background). You’re either using Winsock 1.1 or are dragging forward obsolete

Re: [sqlite] Header corruption

On 17 Apr 2018, at 9:13pm, Peter Da Silva wrote: > Even on Windows, wouldn't doing an ssl_shutdown on a socket you'd already > closed still have a risk of unexpected behavior? Under Windows an attempting to shutdown a connection which is already shutdown returns

Re: [sqlite] Header corruption

On 4/17/18, 3:08 PM, "sqlite-users on behalf of Deon Brewis" wrote: > So this was a special case of re-using the File handle as per the corruption > guide. One just has to be in the mindset that on unix based

Re: [sqlite] Header corruption

> Subject: [sqlite] Header corruption I’m trying to track down SQLITE corruptions that seems to corrupt our databases in a consistent way. (Running on 3.20.1). This isn’t related to a crash or hardware failure. The app is running and reading and writing to the database fine, and then sudde

Re: [sqlite] Header corruption

> On Feb 8, 2018, at 12:43 AM, Eduardo wrote: > > Profiling shouldn't help, it isn't the rigth tool. Use Xcode analyzer or from > command line scan-build and scan-view. If you can, use the last version of > clang-analyzer. The Clang address sanitizer would be

Re: [sqlite] Header corruption

On Wed, 7 Feb 2018 17:29:54 + Deon Brewis escribió: > Oh yeah, I don’t think this is a SQLITE bug or anything. > > I think something in our code is writing to memory after freed. I'm just > trying to track it down at the point that it happens. We've tried all >

Re: [sqlite] Header corruption

To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sqlite] Header corruption On 7 Feb 2018, at 3:16pm, Deon Brewis <de...@outlook.com> wrote: > So this looks more like something is overwriting the memory of Page1 before > SQLITE writes it back to disk. Tha

Re: [sqlite] Header corruption

On 7 Feb 2018, at 3:16pm, Deon Brewis wrote: > So this looks more like something is overwriting the memory of Page1 before > SQLITE writes it back to disk. That is almost always what people eventually admit to after reporting a problem like this. Some part of their code is

Re: [sqlite] Header corruption

Behalf Of Dan Kennedy Sent: Tuesday, February 6, 2018 9:08 AM To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] Header corruption On 02/06/2018 11:57 PM, Deon Brewis wrote: I’m trying to track down SQLITE corruptions that seems to corrupt our databases in a consistent way. (Running

Re: [sqlite] Header corruption

On 2/7/18, Deon Brewis wrote: > > I don't think SQLITE verifies the memory during every write. There's a: > if( memcmp(page1, zMagicHeader, 16)!=0 ){ > > during lockBtree() but that seems to be on read, not write. > > > Is there somewhere I can add a check of the header buffer

Re: [sqlite] Header corruption

the first time? (Seek past the zMagicHeader?). - Deon -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Dan Kennedy Sent: Tuesday, February 6, 2018 9:08 AM To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] Header corruption

Re: [sqlite] Header corruption

On 02/06/2018 11:57 PM, Deon Brewis wrote: I’m trying to track down SQLITE corruptions that seems to corrupt our databases in a consistent way. (Running on 3.20.1). This isn’t related to a crash or hardware failure. The app is running and reading and writing to the database fine, and then

Re: [sqlite] Header corruption

-boun...@mailinglists.sqlite.org] On Behalf Of Deon Brewis Sent: Tuesday, February 06, 2018 11:57 AM To: SQLite mailing list Subject: [sqlite] Header corruption I’m trying to track down SQLITE corruptions that seems to corrupt our databases in a consistent way. (Running on 3.20.1). This isn’t

[sqlite] Header corruption

I’m trying to track down SQLITE corruptions that seems to corrupt our databases in a consistent way. (Running on 3.20.1). This isn’t related to a crash or hardware failure. The app is running and reading and writing to the database fine, and then suddenly we start getting a SQLITE_NOTADB