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,
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
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
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
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
]
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 can have, something has to giv
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
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
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)
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
14 matches
Mail list logo
