---------- Forwarded message ---------- From: <sqlite-users-boun...@sqlite.org> Date: Wed, Apr 6, 2011 at 2:48 PM Subject: Content filtered message notification To: sqlite-users-ow...@sqlite.org
The attached message matched the sqlite-users mailing list's content filtering rules and was prevented from being forwarded on to the list membership. You are receiving the only remaining copy of the discarded message. ---------- Forwarded message ---------- From: Oliver Schneider <oli...@f-prot.com> To: sqlite-users@sqlite.org Date: Wed, 06 Apr 2011 18:48:11 +0000 Subject: Re: [sqlite] Access violation at address 6090B662 in module 'sqlite3.dll'. Read of address DE8D6B84 Hi, On 2011-04-06 18:36, Vander Clock Stephane wrote: > in heavy multithread environnmeent we receive (one time a month, so not > very often), this error : > Access violation at address 6090B662 in module 'sqlite3.dll'. Read of > address DE8D6B84 > > any idea ? my suggestion would be to install the proper exception handlers at the top-level of the application and then use MiniDumpWriteDump to write a dump file. Load that into WinDbg with the proper symbols available in the path and you will learn a lot about where it happens and potentially why. Should this be a heap corruption, things are usually bleak at first, but there are some methods here as well. If your application is cross-platform I strongly suggest to get your hands on Valgrind and run the code under it. It will point out all kinds of issues. If it is not, Application Verifier and some profilers such as AQTime can be of help on Windows in tracking down such issues. Consider that a heap corruption is often caused long before the attempt is made to read/write the corrupted location(s). // Oliver -- D. Richard Hipp d...@sqlite.org
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
