Hi,

I upgraded the SQLite DLL to 3.14.1. The job finished the first time but crashed the second time mentioning sqlite3.dll.

I'm almost out of tracks to follow. Any idea on what I could check next?


Regards and thanks,

Frantz.


On 02/09/2016 11:14, Frantz FISCHER wrote:

Hi,

Tried with the 2.7.12 version but it still fails.

I double-checked I didn't take the wrong version and compared the md5sum of python27.dll with the one from python 2.7.12, they are identical -> 797f4566d81c04ed5f21637d2d64197f

This time the crash didn't generate a dump and points only to sqlite3.dll not the python module.

Also, after comparing python 2.7.12 release notes (sqlite version is 3.8.11.0) and sqlite release notes, the latest sqlite available is 3.14.1 and contains several crash fixes.

Can I simply replace the DLL?

Regards,

Frantz.


On 01/09/2016 17:29, Scott Robison wrote:
In looking at the changelog for 2.7.12, I see multiple SQLite related
Python fixes that addressed coredump bugs.

On Sep 1, 2016 9:22 AM, "Scott Robison"<[email protected]>  wrote:

It appears 2.7.12 is available. Perhaps it is worth trying.

On Sep 1, 2016 9:19 AM, "Frantz FISCHER"<[email protected]>  wrote:

Hello,


2.7.10 python own release.

Got another crash mentioning the _pylite3.pyd module as you suspected
before.


Thanks,

Frantz.


On 01/09/2016 17:00, Scott Robison wrote:

Specifically, what version / distribution of Python 2 is in use? Python's
own release, ActiveState, other?

On Sep 1, 2016 8:27 AM, "Frantz FISCHER"<[email protected]>  wrote:

Hello Richard,
Thank you for your answer!

Could you please tell me which details you would require?

I managed to get a windows mini dump, would that be of any help?

This is the default sqlite3.dll bundled with python 2.7. Do you require
the python module? the dll itself?


Regards,

Frantz.


On 01/09/2016 14:33, Richard Hipp wrote:

On 9/1/16, Frantz FISCHER<[email protected]>   wrote:
Using our client Python app for synchronization with a server it
crashes
frequently generating c0000005 error and also mentioning sqlite3.dll.

Usually when an application crashes and SQLite is mentioned in the
stack trace, that indicates that some other module corrupted the heap
and SQLite was the first unlucky module to stumble over the
corruption.

That said, if you can provide more details, we will look into the
matter.


_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

--

*Frantz Fischer*
Premium Support Team
+33 (0)1 40 33 79 87
+33 (0)1 40 33 71 41 (Fax)
www.nuxeo.com  - Content Management Platform<https://www.nuxeo.com>

_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

--

*Frantz Fischer*
Premium Support Team
+33 (0)1 40 33 79 87
+33 (0)1 40 33 71 41 (Fax)
www.nuxeo.com - Content Management Platform <https://www.nuxeo.com>


--

*Frantz Fischer*
Premium Support Team
+33 (0)1 40 33 79 87
+33 (0)1 40 33 71 41 (Fax)
www.nuxeo.com - Content Management Platform <https://www.nuxeo.com>

_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to