Access violation when building in shared library

[DominicPicard]

Hi,

I have been using sqlite_orm in a library in MSVC C++. Everything is going except when I build a .dll instead of a .lib

I get an access violation exception, this is the callstack :

I searched on google for this specific error but I could not find anything.

I am using Conan to retrieve sqlite3 and sqlite_orm. I use sqlite 3.43.2

I was wondering if anyone has ever seen this weird problem ?

I am starting to panic 😟

[trueqbit]

Did you create sqlite3 with debug symbols (pdb)? I suggest you investigate the context around the crashing code path a bit more. Also try a build without optimizations.

[DominicPicard]

Hi,

Thank you for your quick reply !

I debugged a bit and I see that the address for the global variable sqlite3GlobalConfig changes...

That global variable holds the mutex function pointer which becomes null when it is recreated :

The callstack is the following:

And the exception happens here :

My work around is to call sqlite3_initialize() here :

I think my issue is more related to C/C++, why does that global variable gets recreated ? Do I do something wrong when I include headers/libraries ?

[trueqbit]

Usually, those kind of things rather happen in multithreaded applications. Does this possibly apply to you?
The way connections are currently handled in sqlite_orm requires that you use open_forever() when using multiple threads.

[DominicPicard]

I am not sure what the issue is. I had the same problem when using SQLiteCpp. I changed my design the restrict the database access to the library and not also access the database directly in my unit test application.