Hi,
As Christian said, probably your heap is corrupted. Your backtrace
clearly indicates that.
The typical errors that lead to this are
- you free() some memory twice
- you free more or less memory than you malloc() ed
- you overrun a buffer on the heap
valgrind is a good tool to detect such m
tanx for the advice...but how to avoid heap corruption? and why does it happen?
anyway, finally here is the backtrace:
*** glibc detected *** malloc(): memory corruption: 0x0808e078 ***
Program received signal SIGABRT, Aborted.
[Switching to Thread -1213548864 (LWP 4348)]
0xe410 in __kernel_v
On Mon, 24 Oct 2005 [EMAIL PROTECTED] wrote:
>Hi,
>i have a very strange problem using sqlite with a C application...
>i create a database of images, storing image data and other information about
>it.
> ...in all the attempt of new databases i did, but it was frequently 37),
>during data reading
Hi,
i have a very strange problem using sqlite with a C application...
i create a database of images, storing image data and other information about
it.
If i access to a single row (=3Dimage) of the database, with a single execution
of the program, it's all ok, and i see the selected image.
But if
4 matches
Mail list logo
