> on standard output But how this work in concrete steps? Does code have to be added to SQLite to write for example to a text file? The Explain command doesn't produce this information or can it?
> You did you manage to implement new UDFs if you are not a C programmer? Somebody familiar with C added this to a std_call dll and I picked it up from that via a .tlb file and an ActiveX (VB6) dll. All working fine, except in that mentioned situation. RBS On Tue, Dec 8, 2015 at 10:09 PM, Richard Hipp <drh at sqlite.org> wrote: > On 12/8/15, Bart Smissaert <bart.smissaert at gmail.com> wrote: > > Having a problem where 2 UDF's in one SQL cause a crash in my application > > (Excel) > > originating from SQLite. This is on Windows 7 with the latest SQLite > > version. > > I have a sqlite3.dll compiled with these compiler options: > > > > -DSQLITE_DEBUG > > -DSQLITE_MEMDEBUG > > -DSQLITE_OMIT_LOOKASIDE > > > > I can run PRAGMA vdbe_debug = 1 > > > > But how do I see now any useful debugging information that could make me > > understand > > this crash? I am not a C programmer. Is there an option somewhere to > dump a > > log file? > > The "PRAGMA vdbe_debug=ON;" command should give you copious amounts of > debugging information on standard output. Does it not? > > You did you manage to implement new UDFs if you are not a C programmer? > > -- > D. Richard Hipp > drh at sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
