Thank you all for your inputs. Let me check.
On Wed, Mar 26, 2014 at 2:05 PM, Oliver Schneider
wrote:
> On 2014-03-25 18:52, Larry Brasfield wrote:
>> Going in, it is best to not read too much into your code running
>> "pretty well" on a Unix platform. Have you run your code with
>> Valgrind (or
On 2014-03-25 18:52, Larry Brasfield wrote:
> Going in, it is best to not read too much into your code running
> "pretty well" on a Unix platform. Have you run your code with
> Valgrind (or equivalent) on that platform? If not, doing so may help
> you uncover a bug which affects behavior more bad
>>Quite unlikely is the prospect for somebody here to say "Yes, we
>>routinely see crashes on Windows in the sqlite3_mutex_enter code."
>>You are going to have to debug this.
This. I run the hell out of Sqlite under 32 and 64 bit windows with no
issues. 20-40 GB databases are common with multi-th
durga.disc wrote:
> We have an application on unix platform with sqlite database which
> is running from last 2 years. pretty well.
>
> We recently ported on Windows too. Crashed at inserting record in a
> small database(less than 20 records, record has 10 columns). It's not
> reproducible.
>
>
Hi all,
We have an application on unix platform with sqlite database which
is running from last 2 years. pretty well.
We recently ported on Windows too. Crashed at inserting record in a
small database(less than 20 records, record has 10 columns). It's not
reproducible.
call stack:
ntdll
5 matches
Mail list logo