> On Nov 13, 2018, at 2:18 AM, Hegde, Deepakakumar (D.)
> wrote:
>
> #0 sqlite3DbMallocRawNN (db=db@entry=0x1dea20, n=176093659143
> ) at
> /workspace/workspace/Trigger-Build-Host_Job/host/yunos6.0/third_party/sqlite/sqlite3.c:24732
176093659143 = 0x290007
Looks kind of like it was
Hi All,
We are facing a problem in which sqlite library function sqlite3DbMallocRawNN()
is getting crashed inside the sqlite3_prepare_v2() function to prepare the
statement.
As per the analysis "n" value input to this seems to have a big value causing
the crash. checked the input value to
On 11/13/18, Hegde, Deepakakumar (D.) wrote:
> Hi All,
>
>
> We are facing a problem in which sqlite library function
> sqlite3DbMallocRawNN() is getting crashed inside the sqlite3_prepare_v2()
> function to prepare the statement.
This sort of thing is almost always the result of heap corruption
Hi All,
We are facing a problem in which sqlite library function sqlite3DbMallocRawNN()
is getting crashed inside the sqlite3_prepare_v2() function to prepare the
statement.
As per the analysis "n" value input to this seems to have a big value causing
the crash. checked the input value to
On 3/10/17, Anthrathodiyil, Sabeel (S.) wrote:
> Hi,
> I am facing a crash while invoking "sqlite3_db_release_memory" the crash is
> from pcache1RemoveFromHash. SQLite 3.7.10 is running on ARM A5 with
> Freescale MQX as OS.
>
> Any probable reasons in term of the SQLite
On 10 Mar 2017, at 2:05pm, Anthrathodiyil, Sabeel (S.)
wrote:
> Stack trace is as below
> --
> pcache1RemoveFromHash
> pcache1EnforceMaxPage
> pcache1Shrink
> sqlite3PcacheShrink
>
> The sequence of SQLite operations being followed which lead
Hi,
I am facing a crash while invoking "sqlite3_db_release_memory" the crash is
from pcache1RemoveFromHash. SQLite 3.7.10 is running on ARM A5 with Freescale
MQX as OS.
Stack trace is as below
--
pcache1RemoveFromHash
pcache1EnforceMaxPage
pcache1Shrink
On 08/12/2015 02:15 AM, Robert Weiss wrote:
> The bug seems to be repeatable. At least, it happened again today.
> I haven't used gdb in a long time. Here's my first crack at it; what else
> should I do?
> $ gdb sqliteGNU gdb (GDB) 7.8Copyright (C) 2014 Free Software Foundation,
> Inc.License
It will take a little while to compile with MSVC. ?In the meantime I removed
-DSQLITE_DEFAULT_WORKER_THREADS=4 from the compilation flags and the index was
created successfully. ?Haste makes waste?
Thanks, everyone.Bob Weiss
On Tuesday, August 11, 2015 1:55 PM, Joe Mistachkin wrote:
[continuing from previous gdb output]:(gdb) thread apply all where 15
Thread 6 (Thread 12300.0xa64):#0 ?0x74d66d61 in sysfer!FirstHookFunc () from
/cygdrive/c/Windows/SysWOW64/SYSFER.DLL#1 ?0x in ?? ()
Thread 5 (Thread 12300.0x389c):#0 ?0x77791f92 in
ntdll!ZwWaitForWorkViaWorkerFactory
The bug seems to be repeatable. ?At least, it happened again today.
I haven't used gdb in a long time. ?Here's my first crack at it; what else
should I do?
$ gdb sqliteGNU gdb (GDB) 7.8Copyright (C) 2014 Free Software Foundation,
Inc.License GPLv3+: GNU GPL version 3 or later
Op 11 aug. 2015 17:06 schreef "Robert Weiss" het
volgende:
>
> In the meantime I removed -DSQLITE_DEFAULT_WORKER_THREADS=4 from the
compilation flags and the index was created successfully. Haste makes
waste?
> Thanks, everyone.Bob Weiss
That explains it! Your build of sqlite starts win32
On 08/11/2015 12:23 AM, Robert Weiss wrote:
> Dan Kennedy--
> What address, precisely, should I use to send the database to you? When I
> "reply" to your message I get the whole SQLite discussion group, which is
> what I want to avoid (no offense intended, guys and gals).
> BTW, the problem
Robert Weiss wrote:
>
> [continuing from previous gdb output]:(gdb) thread apply all where 15
> Thread 6 (Thread 12300.0xa64):#0 ?0x74d66d61 in sysfer!FirstHookFunc ()
> from /cygdrive/c/Windows/SysWOW64/SYSFER.DLL#1 ?0x in ?? ()
>
Anyhow, the cause of this appears to be the
Dan Kennedy--
What address, precisely, should I use to send the database to you? ?When I
"reply" to your message I get the whole SQLite discussion group, which is what
I want to avoid (no offense intended, guys and gals).
BTW, the problem does not seem to occur in version 3.8.10.2.
Robert Weiss
On 08/08/2015 04:11 AM, Robert Weiss wrote:
> I observed the sqlite command shell version 3.8.11.1 to crash (exit to the
> OSwithout an error message) while running in a Cygwin shell under Windows 7
> when I tried to create anindex. The source was compiled by gcc 4.9.2. The
> same type of
Op 7 aug. 2015 16:12 schreef "Robert Weiss" het
volgende:
>
> I observed the sqlite command shell version 3.8.11.1 to crash (exit to
the OSwithout an error message) while running in a Cygwin shell under
Windows 7.
Does the same crash occur when using cygwin's SQLite 3.8.10.2 package? In
other
On 7 Aug 2015, at 10:11pm, Robert Weiss wrote:
> And here is the statement thatcaused the crash:
>
> create index d200_on_passport_fn ond200_on_passport(fn);
>
>
>
> The crash didn?t happen when Itried the CREATE INDEX statement on a test
> database with the same ddlstatements but
I observed the sqlite command shell version 3.8.11.1 to crash (exit to the
OSwithout an error message) while running in a Cygwin shell under Windows 7
when I tried to create anindex.? The source was compiled by gcc 4.9.2. ?The
same type of crashhappened when I tried the operation from a Lua
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Richard Hipp
Sent: Wednesday, February 25, 2015 12:53 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] sqlite crash with malloc_printerr in sqlite3MemFree
On 2/25/15, Zhao Lin wrote:
> Hi all,
>
> We
On 2/25/15, Zhao Lin wrote:
> Hi all,
>
> We sometimes, not always reproducible but it does recur from time to time,
> get the following crash stack with sqlite3 version 3.8.1, we couldn't tell
> much from our stack, wondering if there are possibly related bugs on
> sqlite3?
The usual cause of
Hi all,
We sometimes, not always reproducible but it does recur from time to time, get
the following crash stack with sqlite3 version 3.8.1, we couldn't tell much
from our stack, wondering if there are possibly related bugs on sqlite3?
#0 0x7fdd66214925 in raise () from /lib64/libc.so.6
On Tue, Sep 9, 2014 at 10:39 AM, Dominique Devienne
wrote:
> On Tue, Sep 9, 2014 at 1:50 PM, Sebastien David
> wrote:
>
> > I have a database with 10million of row in one table (file size is ~5GB)
> > When I execute a query that should return half of
On Tue, Sep 9, 2014 at 1:50 PM, Sebastien David
wrote:
> I have a database with 10million of row in one table (file size is ~5GB)
> When I execute a query that should return half of this table, sqlite fails
> because at some point there is no memory (this is normal) [...]
Hi,
I have a database with 10million of row in one table (file size is ~5GB)
When I execute a query that should return half of this table, sqlite fails
because at some point there is no memory (this is normal) but instead of
returning an error, it crashes.
sqlite version: 3.7.5
#0
On 5 May 2014, at 6:42am, NULL wrote:
> the attached files is the code i used,and the code would be cause system
> crash when call like this,
> sqlite3_exec(db, "create table hello(one varchar(10), two smallint)",
> callback, 0, )
You cannot attach files to posts to
Hi,
the attached files is the code i used,and the code would be cause system
crash when call like this,
sqlite3_exec(db, "create table hello(one varchar(10), two smallint)",
callback, 0, )
A snapshot of call stack on crash is attached.
Zhouran
On 1 Jan 2012, at 3:49pm, Lalitkumar Choudhary wrote:
> I want to know one thing about sqlite crashing, you had mentioned in your
> document which i had found in your website(www.sqlite.org).
> Sqlite database will crash if you write some garbage value into the file.
Which document on that
On Sun, Jan 1, 2012 at 10:49 AM, Lalitkumar Choudhary <
lalitkumar.choudh...@lnties.com> wrote:
> Hi,
>
> I want to know one thing about sqlite crashing, you had mentioned in your
> document which i had found in your website(www.sqlite.org).
> Sqlite database will crash if you write some garbage
On Sun, Jan 1, 2012 at 4:49 PM, Lalitkumar Choudhary <
lalitkumar.choudh...@lnties.com> wrote:
> ...Sqlite database will crash if you write some garbage value into the
> file. May i know exactly what is the garbage value? Is it any value
> different from datatype or anything else, can u please
Hi,
I want to know one thing about sqlite crashing, you had mentioned in your
document which i had found in your website(www.sqlite.org).
Sqlite database will crash if you write some garbage value into the file. May i
know exactly what is the garbage value? Is it any value different from
Thanks for the report. The current test suite has many cases testing
queries of the form you mention. I added one specifically for the query you
suggested to in4.test. Everything passes for the current version. If you
could test with the latest version of SQLite, it might help show where the
Hi all,
I've hit what I believe may be a crash bug in SQLite. I'm using the version
bundled with Python 2.5.2 on Windows, which is SQLite 3.3.4, it would
appear. I know, this isn't the latest version, but this happens to be the
version bundled with the version of Python my product relies on.
Ok great - I guess I need to check for upgrades more often. And as for
what I was doing - well I have a program that generates queries (not
very well it appears) and it would occasionally crash - when I tracked
the bug down I was able to simplify it to two lines.
Samuel R. Neff wrote:
I
I was using sqlite3.exe on windows xp when I discovered it.
Then, for confirmation, I ran the same set of commands on the same
version of sqlite3 (a version I think I compiled) on a linux machine and
got the same thing.
Then, for further confirmation, I *also* ran it on a FreeBSD machine
Try this:
$ sqlite3
SQLite version 3.4.0
Enter ".help" for instructions
sqlite> create table test (field text);
sqlite> select * from test group by distinct field;
Segmentation fault
$
oops... Any idea?
~chris.
-
To
36 matches
Mail list logo