techi eth wrote: You should compile your code & sqlite3.c with -g -O0 when sending a stack trace.
Most likely, the bug is in your program. Since you're on Linux, try running with valgrind memcheck tool to find bugs (access to free memory, uninitialized memory, etc.) If you compile with clang-3.3 or newer, or gcc-4.8.* or newer, you can also compile & link with -fsanitize=address to find bugs (much quicker than using valgrind if your program is slow). But the best is to try both (valgrind & gcc/clang address sanitizer, not at the same time) since they can find different bugs: * only valgrind will find uninitialized memory access * only the address sanitizer will find global and stack overflows * both will find other kind of errors (double free, use of freed memory...) Dominique > Please provide me hint to solve the issue. > > > Thanks.. > > > On Fri, Oct 11, 2013 at 7:58 PM, techi eth <techi...@gmail.com> wrote: > >> It is giving same trace what i have sent last time. >> >> It is possible by some one to send test code snapshot of scenario of >> selecting user defined function while trigger execution. >> >> Thanks a lot... >> >> >> On Fri, Oct 11, 2013 at 7:41 PM, Richard Hipp <d...@sqlite.org> wrote: >> >>> On Fri, Oct 11, 2013 at 10:06 AM, techi eth <techi...@gmail.com> wrote: >>> >>> > Please provide some hint. >>> > >>> >>> Recompile with -O0 and -g and then post the stack trace after the >>> segfault. >>> >>> -- >>> D. Richard Hipp >>> d...@sqlite.org >>> _______________________________________________ >>> sqlite-users mailing list >>> sqlite-users@sqlite.org >>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >>> >> >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
