-
-
Notifications
You must be signed in to change notification settings - Fork 502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
assertion failed in pqpath.c #188
Comments
Originally submitted by: Edouard Chamillard for reference this is the relevant pqpath.c code block @@@ c
|
I've not been able to reproduce the issue, although I've run psycopg test suite againts Python 3.3. I don't think the block you have reported is the correct one. The one to blame looks:
there is indeed some sort of error as running
the ? at "using cast" is probably the result of a bad dereferencing; probably you are running it in a debug version of python with asserts enabled. I think the above idiom is broken for all Python 3. Mmm... too bad I've overlooked the issue and just released. |
Originally submitted by: Edouard Chamillard the trace was indeed produced by a debug version of python. originally gdb pointed to pqpath.c:1140 which is Py_INCREF(cast); i can try to reproduce the issue and link the whole coredump if you need. |
A script to reproduce the issue would be preferred. A patch to fix the issue would be even better accepted, above all if checking the issue implies recompiling python in debug mode. You'd save me quite some time. I've not understood yet what is the problem though. The problem in the Dprintf is probably just that the name is an unicode object under Py3. But why the incref should fail? |
Fixed in master and maint_2_5. As I expected it was the bad use of Bytes_AS_STRING causing the assertion failure. Tested on a debug build Py3.4. Also found an unrelated bug exposed by debug build, so good stuff. If you can test everything works in your environment it would be great, thank you. |
The way we were doing it is unsafe and causes assertion failures on Py3. Fixes ticket psycopg#188
The way we were doing it is unsafe and causes assertion failures on Py3. Fixes ticket psycopg#188
The way we were doing it is unsafe and causes assertion failures on Py3. Fixes ticket psycopg#188 Conflicts: NEWS
Originally submitted by: Edouard Chamillard
rel-2.5.1 os-linux
celery tasks are using psycopg through sqlalchemy from two different machines. on one it works fine, on the other it segfaults. after a bit of digging a recompiling stuff with debug enabled i got
full trace attached.
The text was updated successfully, but these errors were encountered: