It's caused calling a sqlite_create_module trying to load an extension by
sqlite3 shell.
2012/2/3 Stephan Beal
> 2012/2/3 Jorge Eliécer Osorio Caro
>
> > Good morning every one,
> >
> > I having a issue when try to create a sqlite3_create_module.
> >
> > when try to load my extension im getting
2012/2/3 Jorge Eliécer Osorio Caro
> Good morning every one,
>
> I having a issue when try to create a sqlite3_create_module.
>
> when try to load my extension im getting that error "Segmentation fault",
> cause the sqlite3 cash. i dont know how it happend its my code:
>
> http://paste.ideaslabs.
Good morning every one,
I having a issue when try to create a sqlite3_create_module.
when try to load my extension im getting that error "Segmentation fault",
cause the sqlite3 cash. i dont know how it happend its my code:
http://paste.ideaslabs.com/show/OPNHBY7xPG
__
ced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Christian [siriu...@gmx.de]
Sent: Friday, October 28, 2011 10:08 AM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] S
> Von: "Black, Michael (IS)"
> An: General Discussion of SQLite Database
> Betreff: Re: [sqlite] Segmentation Fault on SQLITE3_exex
> What you're showing should basically work as long it's not a single class
> instantiation being used by multiple threads.
> Al
eral Discussion of SQLite Database; sqlite-users@sqlite.org
Subject: EXT :Re: [sqlite] Segmentation Fault on SQLITE3_exex
First of all thanks for your detailed reply! According to the documentation its
not recommended to reuse a preparedStatement after finalizing it. So my initial
guess to do so
On Fri, Oct 28, 2011 at 10:07 AM, Christian wrote:
> static char command [1024];
> ...
> sprintf (command, "SELECT * from model where id=?");
>
FYI: that can be simplified to:
static char const * command = "SELECT * from model where id=?";
There's no reason why the overhead of sprintf() should
27 Oct 2011 16:00:52 +
> Von: "Black, Michael (IS)"
> An: General Discussion of SQLite Database
> Betreff: Re: [sqlite] Segmentation Fault on SQLITE3_exex
> I think we went throught something similar to this a while ago.
>
>
>
> Does each class have it's
, October 27, 2011 10:24 AM
To: General Discussion of SQLite Database; sqlite-users@sqlite.org
Subject: EXT :Re: [sqlite] Segmentation Fault on SQLITE3_exex
Currently I'm using valgrinds memcheck tools to solve the issue, I already
found some undelete memory which is definitly not ca
;Black, Michael (IS)"
> An: General Discussion of SQLite Database
> Betreff: Re: [sqlite] Segmentation Fault on SQLITE3_exex
>
>
> Then put a breakpoint on the "p" being passed into this function to catch
> when it changesit should only change maybe once during
Information Systems
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Christian [siriu...@gmx.de]
Sent: Thursday, October 27, 2011 6:49 AM
To: General Discussion of SQLite Database; sqlite-users@sqlite.org
Subject: EXT :Re: [sqlite] Segmentation F
Database
> Betreff: Re: [sqlite] Segmentation Fault on SQLITE3_exex
> Me thinkst you're corrupting your stack or memory.
>
>
>
> I'd be willing to bet big money that this is your program causing this as
> there are 1000's of people running that exact same c
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Christian [siriu...@gmx.de]
Sent: Thursday, October 27, 2011 4:51 AM
To: sqlite-users@sqlite.org
Subject: EXT :[sqlite] Segmentation Fault on SQLITE3_exex
Hello everybody,
I'm facing a str
Hello everybody,
I'm facing a strange issue and believe that my setup is somehow wrong. From
time to time my program crashes with segfault when calling:
if (sqlite3_exec (db, "BEGIN TRANSACTION", 0, 0, 0) != SQLITE_OK)
{
//error
}
The stacktrace points to this function:
static void pthreadMute
Richard Hipp escribió:
On Tue, Apr 26, 2011 at 3:18 PM, Neven Boric wrote:
Hi
I'm using Freeswitch, which has an old version of SQLite embedded in its
source code. I'm getting a segmentation fault whenever I do something that
uses triggers. The segmentation fault occurs inside SQLite code (
Richard Hipp escribió:
> On Tue, Apr 26, 2011 at 3:18 PM, Neven Boric wrote:
>
>> Hi
>>
>> I'm using Freeswitch, which has an old version of SQLite embedded in its
>> source code. I'm getting a segmentation fault whenever I do something that
>> uses triggers. The segmentation fault occurs inside
On Tue, Apr 26, 2011 at 3:18 PM, Neven Boric wrote:
> Hi
>
> I'm using Freeswitch, which has an old version of SQLite embedded in its
> source code. I'm getting a segmentation fault whenever I do something that
> uses triggers. The segmentation fault occurs inside SQLite code (strdup gets
> calle
Hi
I'm using Freeswitch, which has an old version of SQLite embedded in its
source code. I'm getting a segmentation fault whenever I do something
that uses triggers. The segmentation fault occurs inside SQLite code
(strdup gets called with a null pointer inside sqlite3ExprListDup).
Freeswicth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Simon wrote:
> Is this a bug? Or do I need to compile the source differently than what the
> README file directs?
The chances that you found a bug in SQLite that noone else nor the test
suite nor valgrind has hit is vanishingly small :-)
> sqli
Hi List, I get the following segmentation fault whenever I exit sqlite3. The
segmentation fault does not seem to happen If I write something to the database
then exit.
sqlite3(27109,0xa000ed88) malloc: *** error for object 0x1806c00: incorrect
checksum for freed object - object was probably mod
This is now officially off-topic since the problem is in the Python
SQLite wrappers and Apache instead of the SQLite C code. Regardless, I
would like to post the cause and solution so that anybody who ends up
here while doing a web search will know the solution.
> Program received signal SIGSEGV,
> Eric Holmberg wrote:
> > PyDict_GetItem (op=0x0, key=0xb7ce82cc) at Objects/dictobject.c:571
> > 571 if (!PyDict_Check(op))
>
> You would need to supply more of the backtrace since the
> calling routine is supplying a null pointer instead of a
> dictionary. Nothing points to SQLit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Holmberg wrote:
> PyDict_GetItem (op=0x0, key=0xb7ce82cc) at Objects/dictobject.c:571
> 571 if (!PyDict_Check(op))
You would need to supply more of the backtrace since the calling routine
is supplying a null pointer instead of a dicti
I'm trying to solve a RedHat Enterprise Linux 4 issue where I have
built, from source, Python 2.5.2, mod_python v3.2.8, and SQLite 3.5.9.
SQLite works fine in the Python 2.5.2 interpreter, but when running from
mod_python (I also tried mod_wsgi), I get a segmentation fault in the
Python file Object
dark0s dark0s wrote:
> I did not used never gdb.
> Can I post me commands that I must to use
OK, you are seriously becoming a help vampire
(http://www.slash7.com/pages/vampires) at this point. Here are some
pointers:
- Programming in C: A Modern Approach
http://knking.com/books/c2/inde
HINT: se a debugger:
for (i=0;i for (i=0;i<=dim;i++) str2[i] = toupper(str2[i]);
str2 is never initialized and hence the assignment above is probably the issue
dark0s dark0s <[EMAIL PROTECTED]> wrote: This is last suggestion that I tell,
where is the problem now for segmentation fault:
I did not used never gdb.
Can I post me commands that I must to use
(gdb) run sqlite3
Starting program: sqlite3
No executable file specified.
Use the "file" or "exec-file" command.
(gdb) run select load_extension('/root/soundex.so');
Starting program: select load_extension('/root/soundex.so');
] segmentation fault
How must I interpret this output:
bash-3.1# gcc -O0 -g -shared labsinf.c -o soundex.so
bash-3.1# gdb sqlite3
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute
How must I interpret this output:
bash-3.1# gcc -O0 -g -shared labsinf.c -o soundex.so
bash-3.1# gdb sqlite3
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of i
"dark0s dark0s" <[EMAIL PROTECTED]> wrote in
message news:[EMAIL PROTECTED]
> This is last suggestion that I tell, where is the problem now for
> segmentation fault:
A few threads back, I predicted precisely this outcome. Writing through
uninitialized pointers tends to end up this way, you know.
k0s
Sent: domingo, 13 de abril de 2008 10:46
To: sqlite-users@sqlite.org
Subject: [sqlite] segmentation fault
This is last suggestion that I tell, where is the problem now for
segmentation fault:
bash-3.1# gcc -shared labsinf.c -o soundex.so
bash-3.1# sqlite3
SQLite version 3.5.7
Enter ".h
This is last suggestion that I tell, where is the problem now for segmentation
fault:
bash-3.1# gcc -shared labsinf.c -o soundex.so
bash-3.1# sqlite3
SQLite version 3.5.7
Enter ".help" for instructions
sqlite> select load_extension('/root/soundex.so');
sqlite> select soundex('saverio');
S010
S
Hi all,
very strange. Today I tried to open a database I created about half a year ago
(version 3.?) and I get a segmentation fault. I run a current debian unstable
with sqlite3.5.7 and have absolutely no clue what the problem might be! It works
with other databases and it worked with that one as w
"Joseph Hsu" <[EMAIL PROTECTED]> wrote:
> Sorry, I use SQLite 3.4.2, NOT SQLite 3.5.2.
> The code in pager.c:2417 (SQLite 3.4.2) is
>
> for(pPg=pPager->pAll; pPg; pPg=pPg->pNextAll){
> pPg->needSync = 0;// <= line 2417
> }
> Is there something wrong to pPg ? why ??
>
We have not re
was occured.
(pPager is the parameter of syncJournal (pPager=0x102028) )
Thanks to Richard to remind me the wrong SQLite version number.
Sincerely yours,
Joseph
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 29, 2007 10:48 PM
Subject: Re: [sqlite] Seg
"Joseph Hsu" <[EMAIL PROTECTED]> wrote:
> Hello,
> I use SQLite 3.5.2 on ARM9 embedded system. ( Linux 2.4 )
> My program sometimes meets segmentation fault ! ( randomly, maybe several
> hours, maybe several days ! )
> Here is a clip from GDB:
> -- snip --
> (gdb) backtrace
> #0 syncJournal (pPag
Hello,
I use SQLite 3.5.2 on ARM9 embedded system. ( Linux 2.4 )
My program sometimes meets segmentation fault ! ( randomly, maybe several
hours, maybe several days ! )
Here is a clip from GDB:
-- snip --
(gdb) backtrace
#0 syncJournal (pPager=0x102028) at src/pager.c:2417
#1 0x0007cbbc in sqlit
"Rich Rattanni" <[EMAIL PROTECTED]> wrote:
> I am wondering why my program crashes with a segmentation fault. This
> has only occured once, but it seems to be something with sqlite. Is
> this a known issue or is there anything I can do to further track this
> down?
>
There are no known malloc()
I am wondering why my program crashes with a segmentation fault. This
has only occured once, but it seems to be something with sqlite. Is
this a known issue or is there anything I can do to further track this
down?
Program terminated with signal 11, Segmentation fault.
#0 0x403cdcb4 in _int_m
On 4/6/06, Dennis Cote <[EMAIL PROTECTED]> wrote:
> No big deal. I thought it was funny (well a little humorous anyway) that
> you did exactly the same thing in the sample code you posted regarding
> the prepare statement tutorial question (only a few minutes apart).
Yeah, I wrote that a while ago
Jay Sprenkle wrote:
On 4/6/06, Dennis Cote <[EMAIL PROTECTED]> wrote:
Jay,
No, he has the open call correct. He has a local pointer, he passes the
address of that pointer to sqlite3_open() and it allocates the sqlite3
structure and sets his pointer to point to it.
No need to change this. D
On 4/6/06, Dennis Cote <[EMAIL PROTECTED]> wrote:
> Jay,
>
> No, he has the open call correct. He has a local pointer, he passes the
> address of that pointer to sqlite3_open() and it allocates the sqlite3
> structure and sets his pointer to point to it.
>
> No need to change this. Derrell has iden
Jay Sprenkle wrote:
> Here you pass the address of db, which is already a pointer.
>
>You've passed a pointer to a pointer but never allocated the structure used.
>
>I think you want to change this:
>
>
>> sqlite3 *db;
>>
>>
>to
>
>
>> sqlite3 db;
>>
>>
Jay,
No, he has the o
On 4/6/06, 杰 张 <[EMAIL PROTECTED]> wrote:
> Hi all,
> I just want to get the values of a table.The result implemented is
> "Open OK!
> segmentation fault ". Why did I got this result ? The following is my code:
>
> #include
> #include
> #include "sqlite3.h"
> main()
> {
> char **er
杰 张 <[EMAIL PROTECTED]> writes:
> 1. (*) text/plain
>
> Hi all,
> I just want to get the values of a table.The result implemented is
> "Open OK!
> segmentation fault ". Why did I got this result ? The following is my code:
Just from a quick visual inspection, it appears that y
Find out yourself :-)
If you are using gcc, add -g flag when compiling, and then run it using gdb:
gdb your-executable
and then
> run
and then when it give the seg-fault, run:
> backtrace
This will give you a good hint about what is wrong.
Ran
On 4/6/06, 杰 张 <[EMAIL PROTECTED]> wrote
Hi all,
I just want to get the values of a table.The result implemented is "Open
OK!
segmentation fault ". Why did I got this result ? The following is my code:
#include
#include
#include "sqlite3.h"
main()
{
char **errmsg;
int ret;
int rc;
sqlite3 *db;
char *
Am 02.08.2005 um 19:18 schrieb D. Richard Hipp:
On Tue, 2005-08-02 at 09:30 -0400, D. Richard Hipp wrote:
On Mon, 2005-08-01 at 22:04 +0200, Jens Miltner wrote:
we get an assertion (no crash here, though) in btree.c
and the backtrace looks similar to the one scunacc provided, which
made me
Dear Kervin,
> What does the the 'where' command say?
(See the original start of the thread for the whole kaboodle), but
here's the offending select:
select
r.kp,
substr(r.kp,1,13) as records,
r.result2,
r.result4,
r.result12,
min(1,(r.arecords2/100)) as ap2,
min(1,(r.arecords4/
Dear Richard,
> Patches to fix ticket #1346 are available at
> http://www.sqlite.org/cvstrac/chngview?cn=2573
> Please try adding these patches and see if they do not
> fix the problem in the multi-threaded application.
Some results. (and bear in mind that I'm not sure that
my particular core d
On Tue, 2005-08-02 at 09:30 -0400, D. Richard Hipp wrote:
> On Mon, 2005-08-01 at 22:04 +0200, Jens Miltner wrote:
> > we get an assertion (no crash here, though) in btree.c
> > and the backtrace looks similar to the one scunacc provided, which
> > made me think the two might be related...
>
>
On Mon, 2005-08-01 at 22:04 +0200, Jens Miltner wrote:
> we get an assertion (no crash here, though) in btree.c
> and the backtrace looks similar to the one scunacc provided, which
> made me think the two might be related...
I am able to reproduce the bug described in ticket #1346.
It looks li
Sorry, I read your trace wrong, thought the
debugger was complaining.
What does the the 'where' command say?
scunacc wrote:
Dear Kervin,
Can you run the sqlite3 under dbx? You may have better luck
getting a backtrace that way instead of reading the core file
after the crash. eg. 'dbx -r sql
Dear Patrick,
> Could you download 2.8.16 and let us know if your process works with
> that version? If so it may be the same issue and might raise the
> visibility. With the performance improvements I'd much rather be on
> the latest version.
Unfortunately it won't help. The application requires
unacc [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 02, 2005 7:16 AM
To: Christian Smith
Cc: sqlite-users@sqlite.org
Subject: Re: [sqlite] Segmentation fault on large selects
Dear Christian,
> Doesn't matter how much memory you have. If ulimits restrict how much
> memory a process c
Dear Christian,
> Doesn't matter how much memory you have. If ulimits restrict how much
> memory a process can have, something has to give. Try:
The process has unlimited ulimits.
Thanks for the suggestion, but other Perl scripts that run already use
huge amounts of memory on this machine, so
On Mon, 1 Aug 2005, scunacc wrote:
>Dear Jay,
>
>> Are you running out of memory?
>
>The machine has 6GB...
>
>I don't think so. It's possible.
>
>Actually, since the query will run with the 64-bit command line version
>I don't *think* so.
>
>Thanks for the thought though.
Doesn't matter how muc
Dear Kervin,
> Can you run the sqlite3 under dbx? You may have better luck
> getting a backtrace that way instead of reading the core file
> after the crash. eg. 'dbx -r sqlite3' or something similar.
Thanks for the suggestion, but I already tried that with exactly the
same results.
Kind regard
Am 01.08.2005 um 21:41 schrieb Kervin L. Pierre:
scunacc wrote:
I have built with debugging on, and can't do anything with the
core dump:
dbx Type 'help' for help.
enter object file name (default is `a.out', ^D to exit): sqlite3
reading symbolic information ...
[using memory image in core]
scunacc wrote:
I have built with debugging on, and can't do anything with the core
dump:
dbx
Type 'help' for help.
enter object file name (default is `a.out', ^D to exit): sqlite3
reading symbolic information ...
[using memory image in core]
Illegal instruction (reserved addressing fault) i
Dear Jay,
> Are you running out of memory?
The machine has 6GB...
I don't think so. It's possible.
Actually, since the query will run with the 64-bit command line version
I don't *think* so.
Thanks for the thought though.
Kind regards
Derek Jones.
On 7/31/05, scunacc <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> SQLite is wonderful. Thank you for this piece of software.
>
> I have a problem however with large tables > 1M rows.
Are you running out of memory?
Dear all,
SQLite is wonderful. Thank you for this piece of software.
I have a problem however with large tables > 1M rows.
I am using the latest of everything:
SQLite 3.2.2
DBI 1.48
DBD::SQLite 1.09
AIX 4.3.3
Native C compiler.
The Perl is one rev behind at 5.8.6 but I get an identical issue
A simple program like the bellow, gives a SIGSEGV when running with gdb:
handle = sqlite_open("testc.db",0,NULL);
sqlite_exec(handle,"Create Table Test (Code Integer , Memo
Text);",NULL,NULL,NULL);
printf("Created Simple Table\n");
sqlite_close(handle);
return 0;
backtrac
101 - 164 of 164 matches
Mail list logo
