That I can demonstrate all day long.. but I'd have to show that the issue is
their library causing the issue, so I'd need to demonstrate the shell executing
the commands okay without their library attached.. and then failing with it
attached. For instance if I have my program running with their library
attached and it fails.. and I run SQLiteStudio at the same time which is in a
separate process.. SQLiteStudio can read my database fine.
Their argument was that it's related to my DLL's exported symbols (which I
checked out and they look fine)? My gut feeling is that one of us has to
rename all Sqlite3 static function names and variables to avoid conflicts and
recompile. Since they make the library which should work with their users
using stock Sqlite3 code.. they should do that :^)
Thanks,
Rail
-------------------------------------------------
On Apr 6, 2016, at 1:48 AM, Simon Slavin <slavins at bigfraud.org> wrote:
>
> On 6 Apr 2016, at 9:41am, Rail Jon Rogut <sqlite3 at platinumsamples.com>
> wrote:
>
>> I'll have to figure out a method to use the Shell Tools inside my program -
>> with the 3rd party DLL linked and running.
>
> I don't mean for production work. I mean you should use it to reproduce your
> problem situation. Just use it to open the file and execute a SELECT or
> INSERT or something. If it crashes with 'disk IO error' you've demonstrated
> the problem to the 3rd party developers. If it doesn't crash you know
> there's something wrong with your own code.
>
> Though it is scriptable from the command line so you /could/ perhaps use it
> for useful things.
>
> Simon.
> _______________________________________________
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
