David Clark wrote:
>
> So I want to debug into it...but debugging into a file bigger than 65000
> lines does not work at all on visual studio 2008.
>
Using the latest trunk, you can work around this issue with Visual Studio by
using the following make command:
nmake /f Makefile.msc
I am trying to compile the source tree on visual studio with makefile.msc and I
get the following:
C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>nmake -B -f make
file.msc | more
Microsoft (R) Program Maintenance Utility Version 9.00.30729.01
Copyright (C) Microsoft Corporation.
Hi, Joe,
Now, it's been years since I've touched VBScript, but I think the syntax of
attributing the connection string to the Open method is wrong. You should
probably use
objConn.Open "Provider=System.Data.SQLite; Data
Source=C:\DATA\SQLLite\mydb.db3"
or (better)
Raheel Gupta wrote:
> Sir, is there any way to not allow malloc to hold memory ? I mean shouldnt
> free(), be freeing the memory ?
free() frees memory in the heap, making it available to other
malloc again. But it does not necessarily shrink the amount of
memory used by the
On Tue, Oct 29, 2013 at 01:22:39AM +0530, Raheel Gupta wrote:
> Sir, is there any way to not allow malloc to hold memory ? I mean shouldnt
> free(), be freeing the memory ?
No. The way malloc() typically works is that it allocates large chunks
of memory from the OS's kernel, then it allocates
On Sat, Oct 26, 2013 at 11:17 AM, Ferdinand Hübner <
ferdinand.hueb...@gmail.com> wrote:
> A query against the xbmc database doesn't return results anymore when
> sqlite-3.8.1 is used. With sqlite-3.8.0.2, the query returns results
> against the identical database just fine.
>
Confirming that
On 28/10/2013 3:57 PM, Richard Hipp wrote:
On Mon, Oct 28, 2013 at 3:52 PM, Raheel Gupta wrote:
Sir, is there any way to not allow malloc to hold memory ? I mean shouldnt
free(), be freeing the memory ?
You'lll need to speak with the developers of your libc
On Mon, Oct 28, 2013 at 3:52 PM, Raheel Gupta wrote:
> Sir, is there any way to not allow malloc to hold memory ? I mean shouldnt
> free(), be freeing the memory ?
>
You'lll need to speak with the developers of your libc implementation about
that.
--
D. Richard Hipp
Sir, is there any way to not allow malloc to hold memory ? I mean shouldnt
free(), be freeing the memory ?
On Tue, Oct 29, 2013 at 1:19 AM, Richard Hipp wrote:
> On Mon, Oct 28, 2013 at 3:47 PM, Raheel Gupta wrote:
>
> >
> > Then I ran "Pragma
On Mon, Oct 28, 2013 at 3:47 PM, Raheel Gupta wrote:
>
> Then I ran "Pragma shrink_memory"
>
> Memory Used: 152584 (max 131658680) bytes
> Number of Outstanding Allocations: 79 (max 2081)
>
So, after running "PRAGMA shrink_memory", SQLite has
Hi,
After running my query :
Memory Used: 131655360 (max 131656000) bytes
Number of Outstanding Allocations: 2079 (max 2081)
Number of Pcache Overflow Bytes: 131567752 (max 131567752) bytes
Number of Scratch Overflow Bytes:0 (max 0) bytes
Largest Allocation:
Okay, let me try that. I will report back. By the way the tool I am using is
a Firefox add in called Sqlite Manager
(https://code.google.com/p/sqlite-manager/). Didn't know there was a tool that
you guys support.
-Original Message-
From: sqlite-users-boun...@sqlite.org
On Mon, Oct 28, 2013 at 9:16 AM, Raheel Gupta wrote:
> >> Whether or not free() returns that space to the operating system or
> keeps
> it around to satisfy future malloc() calls is a detail of the
> implementation of free().
>
> Sir, anyway to be sure of that ?
>
> In the
>> Whether or not free() returns that space to the operating system or keeps
it around to satisfy future malloc() calls is a detail of the
implementation of free().
Sir, anyway to be sure of that ?
On Mon, Oct 28, 2013 at 5:45 PM, Richard Hipp wrote:
> On Mon, Oct 28, 2013
On Mon, Oct 28, 2013 at 9:02 AM, Mike Clagett wrote:
> Well, the text for the index issued from the program is constructed
> programmatically, so I'm going to provide the actual text as seen in the
> Visual Studio debugger just before it is sent to Sqlite.
>
> The
Well, the text for the index issued from the program is constructed
programmatically, so I'm going to provide the actual text as seen in the Visual
Studio debugger just before it is sent to Sqlite.
The actual text, as seen in VisualStudio's debugger, is:
CREATE INDEX
On Mon, Oct 28, 2013 at 8:13 AM, Raheel Gupta wrote:
> >> Then you have answered your question. The amount of memory still being
> used is the size of the cache.
>
> Sir, that is the PEAK usage it goes upto.
> After "PRAGMA shrink_memory" it goes down only to 65MB, which is
>> Then you have answered your question. The amount of memory still being
used is the size of the cache.
Sir, that is the PEAK usage it goes upto.
After "PRAGMA shrink_memory" it goes down only to 65MB, which is 1000 Pages
as per 64K page sizes.
Shouldnt it go down to the original usage of around
On 28 Oct 2013, at 10:45am, Raheel Gupta wrote:
>>> PRAGMA cache_size
>
> I have set that 2000 in both cases.
Then you have answered your question. The amount of memory still being used is
the size of the cache.
Simon.
___
>> If you multiply that by your page size do you get the amount of memory
you see being used
During peak usage the memory reaches 126 MB which is similar to 2000 x 64K.
After "PRAGMA shrink_memory" it goes down only to 65MB, which is 1000 Pages
as per 64K page sizes.
On Mon, Oct 28, 2013 at
>> PRAGMA cache_size
I have set that 2000 in both cases.
On Sun, Oct 27, 2013 at 7:49 PM, Simon Slavin wrote:
>
> On 27 Oct 2013, at 5:10am, Raheel Gupta wrote:
>
> > But why would this happen with 64K pages ? In 1024 Sqlite is able to
> > release
On 10/28/2013 02:19 AM, Tim Streater wrote:
On 27 Oct 2013 at 18:29, Ulrich Goebel wrote:
What I'm looking for is a bash-like frontend for SQLite. The sqlite3
does in principle what I want, but to test queries it would be very nice
to have a history of the commands
22 matches
Mail list logo