Hi Richard,
I tried to open my database file "test.11" by enabling MEMORY_DEBUG=2, it works fine
now.
I was trying to use memory pools for sqliteMalloc. So I modified the malloc & free
calls to my internal memory pool calls. In addition to that I saw that some files were
not calling sqliteMalloc but call malloc directly. I modified all the malloc calls to
sqliteMalloc.
When I use my allocation library call, I do not see any allocation failures but
sqlite_open fails to the follow the sequence of instructions you said that each time
it should follow.
I will try to debug and see what goes wrong when I use a memory pool allocation
mechanism.
Thanks for your reply,
vt
"D. Richard Hipp" <[EMAIL PROTECTED]> wrote:
v t wrote:
> Anybody please help.
>
> I get this error during sqlite_open for an exisitng database.
>
> db=sqlite_open("/ata0/test.11",0,&f)
>
> f points to string "too few operands on stack at 13"
>
> Following is trace:
>
> OPEN 15 /ata0/test.11
> OPEN-EX 16 /temp/saRUxt
> READ 15 1 2
> READ 15 2 0
>
> 0 ColumnName 4 0 1
> 1 Integer 1 0
> Stack: i:1
> 2 OpenRead 0 2 sqlite_temp_master
> 3 Rewind 0 7
> 7 Close 0 0
> 8 Integer 0 0
> Stack: i:0
> 9 OpenRead 1 2 sqlite_master
> 10 VerifyCookie 0 75
> 11 Rewind 1 15
> 12 Integer 0 0 0
> Stack: si:0
> 13 Callback 5 0
> CLOSE 15
> CLOSE 16
>
If possible, please e-mail me your "/ata0/test.11" file.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
