-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/28/2015 01:48 AM, Lohmann, Niels, Dr. (CQTN) wrote: > #0 0x010385c4 in SignalProcmask_r () from > C:\QNX650\target\qnx6/armle-v7/lib/libc.so.3
Have you tried turning off all compiler optimisations? Some older/embedded system compilers can produce crashing code. > #8 0x78991330 in ?? () from libsqlite_shared.so Cannot access > memory at address 0x329457c One possible way this can happen is if shared libraries get unloaded. I experienced this in the past with an Apache module where it got loaded to parse its configuration, then got unloaded, then reloaded to actually use it. Address space randomisation meant it got loaded at a different address. Things got very interesting trying to debug what was going on. > Meanwhile, we found out that replacing "file::memory:?cache=shared" > by "file::memory:" may avoid the problem. We have not tested it > thouroughly. What do you think? The chances of it being an SQLite issue are *very* slim, but not non-existent. SQLite is used all over the place (many billions of apps), and they all use sqlite3_open, although way fewer use the shared cache. Also https://www.sqlite.org/testing.html This is far more likely an issue with the platform (QNX 6.5 is not the most recent release), compiler or your app itself. Stray writes from elsewhere in the app code can easily cause problems within SQLite which does a lot of checking. A strong memory checking tool like Valgrind makes them relatively easy to find. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlYw/voACgkQmOOfHg372QS2CwCghtnlWi00gtYawiuDX+M4/jMp dX4AnRbX1vGnFzz45QUwZOO6WIgnRrOw =C6a8 -----END PGP SIGNATURE-----
