Note this has been sent to the SQLITE Users digest, as well as the comp.lang.tcl newsgroup.
I'm getting a core dump at the end of execution of a script which opens an SQLite database, and performs a query. The gdb stacktrace is as follows: #0 0x284099c0 in ?? () #1 0x2804f918 in dlopen () from /libexec/ld-elf.so.1 #2 0x2804e520 in dlclose () from /libexec/ld-elf.so.1 #3 0x2814a05d in TclpUnloadFile () from /usr/local/lib/libtcl8.5.so #4 0x2810aaef in TclFinalizeLoad () from /usr/local/lib/libtcl8.5.so #5 0x280dc705 in Tcl_Finalize () from /usr/local/lib/libtcl8.5.so #6 0x280dc816 in Tcl_Exit () from /usr/local/lib/libtcl8.5.so #7 0x280a8b56 in Tcl_ExitObjCmd () from /usr/local/lib/libtcl8.5.so #8 0x2809c54d in TclEvalObjvInternal () from /usr/local/lib/libtcl8.5.so #9 0x2809d0c4 in TclEvalEx () from /usr/local/lib/libtcl8.5.so #10 0x2809d3fe in Tcl_EvalEx () from /usr/local/lib/libtcl8.5.so #11 0x281068e0 in Tcl_FSEvalFileEx () from /usr/local/lib/libtcl8.5.so #12 0x2810cbc0 in Tcl_Main () from /usr/local/lib/libtcl8.5.so #13 0x0804869f in main () I get the required output, as the script actually runs to completion, and apparently correctly -- but dumping core is not a good way to end a script (IMHO). Does this signature remind anyone of similar behaviours? I've tried commenting out the close at the end of the script, thinking that the core was happening at the unload of the libtclsqlite3.so code, but I'm not entirely sure what's happening here ... I did previously have a threads related problem with SQLite on FreeBSD, but that was worked around within the mutex code of the SQLite library. Hmmm ... any pointers appreciated. Cheers, Rob Sciuk _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
