(Forwarded this message to the mailing list. My bad.) Hi!
The program doesn't use any dynamic memory allocation at all (besides SQLite3 and another library of mine). It doesn't make any sense. I attached the main.c which is used to call SQLite3. And yes, I know it's pretty crappy code :-). There might be something funny around because of the debugging and stuff. Thanks for your help! - Toni Spets On 6/11/05, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > On Sat, 2005-06-11 at 21:33 +0300, Toni Spets wrote: > > > Here is a clip from GDB: > > -- snip -- > > Program received signal SIGSEGV, Segmentation fault. > > 0xb7ebb03e in mallopt () from /lib/libc.so.6 > > (gdb) bt > > #0 0xb7ebb03e in mallopt () from /lib/libc.so.6 > > #1 0xb7eb9c9f in free () from /lib/libc.so.6 > > #2 0xb7fa7cf3 in sqlite3FreeX (p=0xb7f6caa4) at util.c:287 > > > The funny thing is, that this loop works fine for like 5 minutes and > > then crashes at random place. Am I missing something (like free()ing) > > or is the SQlite3 really forgetting something. > > > > This might be a problem with SQLite. But a more likely > explanation is that something in your program is munging > the malloc memory pool. Perhaps your program is freeing > some memory twice, or continuing to use (and modify) memory > after it is freed, or overrunning a buffer obtained from > malloc(). > -- > D. Richard Hipp <[EMAIL PROTECTED]> > >
