The GDB report is shown as below.
Program terminated with signal 7, Bus error.
#0 0x1009fcd4 in sqlite3WalRead (pOut=,
nOut=, pInWal=,
pgno=, pWal=) at sqlite3.c:43910
43910 sqlite3.c: No such file or directory.
in sqlite3.c
(gdb) bt
#0 0x1009fcd4 in sqlite3WalRead (pOut=,
The GDB report is shown as below.
Program terminated with signal 7, Bus error.
#0 0x1009fcd4 in sqlite3WalRead (pOut=,
nOut=, pInWal=,
pgno=, pWal=) at sqlite3.c:43910
43910 sqlite3.c: No such file or directory.
in sqlite3.c
(gdb) bt
#0 0x1009fcd4 in sqlite3WalRead (pOut=,
The version is 3.7.5
The GDB core dump is shown as below.
gdb) bt
#0 0x36a86b04 in raise () from /lib/libc.so.6
#1 0x36a882f4 in abort () from /lib/libc.so.6
#2 0x36a7e2a4 in __assert_fail () from /lib/libc.so.6
#3 0x100dc958 in btreeInvokeBusyHandler ()
#4 0x1013f1f4 in sqlite3VdbeHalt ()
#5
Version is 3.5.7
journal mode = DELETE
SELECT sqlite_source_id(); 2011-01-28 17:03:50
ed759d5a9edb3bba5f48f243df47be29e3fe8cd7
static int btreeInvokeBusyHandler(void *pArg){
BtShared *pBt = (BtShared*)pArg;
assert( pBt->db );
assert( sqlite3_mutex_held(pBt->db->mutex) );
return
Version is 3.5.7
journal mode = DELETE
SELECT sqlite_source_id(); 2011-01-28 17:03:50
ed759d5a9edb3bba5f48f243df47be29e3fe8cd7
-DSQLITE_THREADSAFE=1 in Makefile
static int btreeInvokeBusyHandler(void *pArg){
BtShared *pBt = (BtShared*)pArg;
assert( pBt->db );
assert(
Please neglect the previous 2 emails. Sorry for the inconvenience.
Version is 3.5.7
journal mode = DELETE
SELECT sqlite_source_id(); 2011-01-28 17:03:50
ed759d5a9edb3bba5f48f243df47be29e3fe8cd7
-DSQLITE_THREADSAFE=1 in Makefile
static int btreeInvokeBusyHandler(void *pArg){
BtShared *pBt =
I believe it is a bug in 3.7.5. It didn't happen in 3.6.22. It causes core dump
when using "BEGIN DEFERRED TRANSACTION" in one of our application to access DB
periodically(every 1 second) . There are other applications access the same DB
periodically but using "BEGIN EXCLUSIVE/IMMEDIATE
A script was running for a heavy load DB access. As you can see the sql
statement "select * from service_table where service_no = '13';" in the log.
There is no rows for service_no 13 or 7 in service_table when it is accessed.
The logic is check the entry is there or not, if not then insert
There is a problem for reply in the web. So I resend again. Please neglect the
previous one. It's 3.7.5. Journal mode is delete not WAL.
A script was running for a heavy load DB access. As you can see the sql
statement "select * from service_table where service_no = '13';" in the log.
There
I have sent the core dump in the previous email. And I found that one thread
receives an event and access DB at the same time with another thread accesses
the same DB. It happens in the heavy load for DB access. Is there a way to
prevent this core dump?
ChingChang
Version is 3.7.5
journal
Please neglect the previous email. Two threads are in the different DB
handler(FD).
I have sent the core dump in the previous email. And I found that one thread
receives an event and access DB at the same time with another thread accesses
the same DB. It happens in the heavy load for DB
The purpose of function antok is that solve the problem of "order by cli_id".
Function antok converts,
X86-1 -> x186-01
X86-2 -> x186-02
X86-10 -> x186-110
X86-111 -> x186-2111
X86- -> x186-3
1.1/12-ds3 -> 01.01/112-ds03
Examples,
Input cli_id x86-2, x86-10, x86-1
Order by cli_id
Do you know why it goes to core dump?
ChingChang
The source code is shown as below,
vector dbStatements;
dbStatements.push_back( "BEGIN TRANSACTION;" );
for ( int x = 0; x < 10; x++ ) {
sprintf( tempString,
"update utilization_table set utilization=%5.2f,sample=%d where
I can't reply in my system, so I create the problem description again.
I miss one source code line "char tempString[1024];"in the last email. The
code dump happened after 4 days' run in a test script not immediately. The
SQLITE statements seem to be ok. Could be a performance issue?
I can't reply in my system, so I create the problem description again.
I miss one source code line "char tempString[1024];"in the last email. The
code dump happened after 4 days' run in a test script not immediately. The
SQLITE statements seem to be ok. Could be a performance issue?
I can't reply in my system, so I create the problem description again.
It seems it's not the problem of sprintf. If it comes from sprintf array size,
the core dump will be like this " in __stack_chk_fail () from /lib/libc.so.6".
The code dump happened after 4 days' run in a test script, not
select * from service_table a,service_fib_table b where
a.service_no=b.service_no;
In this statement, the entry of service_fib_table must be existing to get the
service_table and service_fib_table data.
How can I write in one statement to get the service_table data no matter what
the entry
e] get the data anyway no matter what the entry of the
second table is existing or not
On 9/22/15, John McKown wrote:
> On Tue, Sep 22, 2015 at 3:15 PM, ChingChang Hsiao <
> ChingChang.Hsiao at overturenetworks.com> wrote:
>>
>> How can I write in one statement to get the servic
I have 2 similar tables. If_idx is the key. I am trying to synchronize the
rows. Is there one sql statement to delete the extra row or 2 statements to get
the result for the extra if_idx, 29 and then delete it from the table
lldp_stats_tx_port_table_clear.
PRAGMA foreign_keys=OFF;
BEGIN
CREATE TABLE service_table (
service_nameTEXT, /* name of the service (unique) */
service_no INTEGER, /* internal service number, assigned by the
system. */
service_typeTEXT, /* Type of Service. Should be one of
CREATE TABLE service_table (
service_nameTEXT, /* name of the service (unique) */
service_no INTEGER, /* internal service number, assigned by the
system. */
service_typeTEXT, /* Type of Service. Should be one of
There are 2 related table above. There are service_no 1,2,3,5. Service 1,2,3
are type e-line, service 5 is type e-lan. Service 1,2,3 own 2
service_port(sp_no 1,2). Service 5 owns 3 service_port(sp_no 1,2,3).
What is the count of services have more than 2 service_port(sp) and type is
e-lan?
I have 2 similar tables. If_idx and dest_addr_idx are the keys. I am trying to
synchronize the rows. Is there one sql statement to delete the extra row or 2
statements to get the result for the extra if_idx, 69 and dest_addr_idx ,1 and
then delete it from the table
program to crash
(3) Send me the new stack trace that shows exactly which line the error occurs
on
(4) Also send the sqlite_source_id() for the specific version of SQLite you are
using.
On 8/3/16, ChingChang Hsiao <chs...@advaoptical.com> wrote:
> Our sqlite version is "SQLite v
Our sqlite version is "SQLite version 3.8.8.1".
Modify a configuration data while reading a big configuration DB(show
configuration). It goes to busyhandler and write is successful and read
configuration codes goes to core dump. Is there any idea why going to core
dump? Is something to do
25 matches
Mail list logo