On Fri, May 10, 2013 at 6:41 AM, <bardzotajneko...@interia.pl> wrote:
> > Select below crashes sqlite: > C:\>sqlite3.exe db > SQLite version 3.7.16.2 2013-04-12 11:52:43 > Enter ".help" for instructions > Enter SQL statements terminated with a ";" > sqlite> SELECT `czy firma upadła` FROM `tabela_analityczna`; > Works fine for me on both Linux and Windows7, for SQLite version 3.7.16.2 and 3.7.17 (beta). Running on linux with valgrind gives no warnings. Renaming your database as "pl1.db" and putting your single query in a script named "pl1.txt": drh@tallis:~/sqlite/bld$ valgrind ./sqlite3 pl1.db <pl1.txt ==13669== Memcheck, a memory error detector ==13669== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==13669== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==13669== Command: ./sqlite3 pl1.db ==13669== 0 0 0 0 0 0 0 0 0 0 0 0 0 ==13669== ==13669== HEAP SUMMARY: ==13669== in use at exit: 310 bytes in 12 blocks ==13669== total heap usage: 345 allocs, 333 frees, 153,866 bytes allocated ==13669== ==13669== LEAK SUMMARY: ==13669== definitely lost: 60 bytes in 1 blocks ==13669== indirectly lost: 240 bytes in 10 blocks ==13669== possibly lost: 0 bytes in 0 blocks ==13669== still reachable: 10 bytes in 1 blocks ==13669== suppressed: 0 bytes in 0 blocks ==13669== Rerun with --leak-check=full to see details of leaked memory ==13669== ==13669== For counts of detected and suppressed errors, rerun with: -v ==13669== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2) -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
