It will take a little while to compile with MSVC. ?In the meantime I removed
-DSQLITE_DEFAULT_WORKER_THREADS=4 from the compilation flags and the index was
created successfully. ?Haste makes waste?
Thanks, everyone.Bob Weiss
On Tuesday, August 11, 2015 1:55 PM, Joe Mistachkin <sqlite at
mistachkin.com> wrote:
Robert Weiss wrote:
>
> [continuing from previous gdb output]:(gdb) thread apply all where 15
> Thread 6 (Thread 12300.0xa64):#0 ?0x74d66d61 in sysfer!FirstHookFunc ()
> from /cygdrive/c/Windows/SysWOW64/SYSFER.DLL#1 ?0x00000000 in ?? ()
>
Anyhow, the cause of this appears to be the "sysfer.dll", which belongs to
Symantec Network Threat Protection (NTP):
http://www.symantec.com/connect/forums/weve-found-new-big-one#comment-504141
1
I'm not exactly sure what is causing the bad interaction here; however, it
is possible that Cygwin and Symantec are attempting to hook similar Win32
APIs, with unpredictable results.
Does this issue occur when running a build of SQLite on your machine without
Cygwin (i.e. built using MSVC)?
--
Joe Mistachkin
_______________________________________________
sqlite-users mailing list
sqlite-users at mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
