I was testing a custom SQLite with the test files and one of the file(tclsqlite.test) gave a segmentation fault, when I used Valgrind, it didn't give any stack trace but instead gave the following error.
==5697== ==5697== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==5697== Access not within mapped region at address 0xFFE767F58 ==5697== at 0x4A1CDC: sqlite3VdbeExec (stdio2.h:104) ==5697== If you believe this happened as a result of a stack ==5697== overflow in your program's main thread (unlikely but ==5697== possible), you can try to increase the size of the ==5697== main thread stack using the --main-stacksize= flag. ==5697== The main thread stack size used in this run was 8388608. Can anyone kindly tell what does above error mean? I was not able to find the position of the segmentation fault, will gdb help in this case? Can anyone kindly tell how to use gdb for .test files in order to find origin of the error?
