On Tue, Dec 8, 2015 at 4:30 PM, Bart Smissaert <bart.smissaert at gmail.com>
wrote:
> So, what/where is that standard output channel?
> This is on a Win7 machine. How do I bring up that console window?
> There is no development environment here. I am running this from Excel.
> So, I have a standard Windows sqlite3.dll, a std_call dll (to make SQLite
> accessible to VB6)
Are you using Excel or VB6? They're very different things.
You could try adding something like the following to somewhere near
the beginning of sqlite3_initialize
freopen("sqlite_stdout.txt","a",stdout);
freopen("sqlite_stderr.txt","a",stderr);
This will create two text files for all of sqlite's output. There
might be side effects to doing this .. honestly I have no idea if
it'll work, and finding where the files are created might be
interesting (they'll be the current directory, but I have no idea what
that is when you're running Excel, or VB6)
Really, this problem is best solved with a debugger. Even windbg is
better than flying blind, and you can step through the sqlite code in
a debug build even if it's being loaded by something like Excel where
you don't have the source code.
