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
python-2.7.3-r3: crash in visit_decref() #61436
Comments
Hi, (gdb) where |
Sorry, but this doesn't give enough information to fix it, nevertheless reproduce it. Please tell us what Python was running. Also run python with -X faulthandler and give the results. |
Oops. Please ignore the sentence about adding -X faulthandler. Please install the faulthandler module [0] and run "import faulthandler;faulthandler.enable()", and then reproduce the bug. |
Are you using any 3rd party components with C extension modules? That kind of error is often caused by an extension with erroneous reference counting. |
Hi Ramchandra and Christian, Here is one stacktrace I just got with the faulthandler installed. It does not show in the trace any 3rd-party module so can I conclude it is a core python bug? Just recompiling with "-ggdb" so eventually will have better stacktraces. Does this help? I don't have the gdb stacktrace as I recompiled the binary now again ... :( Fatal Python error: /mnt/1TB/var/tmp/portage/dev-lang/python-2.7.5-r2/work/Python-2.7.5/Objects/dictobject.c:1009 object at 0x40c0a60 has negative ref count -1 |
I'm a C noob but I think one can't conclude that it is a core python bug as the ref count could have been messed with, then sometime later the error may occur and GDB's stacktrace will show the latter. mess_with_ref_count() # In 3rd party code
non_3rd_party_code() #the error may occur here, after the refcount was messed with, and gdb will show this function in the stack trace BTW, run ./configure with the --with-pydebug option, that makes Python perform extra checks on refcounts and other things [0] ^0 http://docs.python.org/devguide/setup.html#compiling-for-debugging |
I'm guessing that the status was inadvertently changed as this issue is only one year old. Could someone set it to open please. |
Should this be closed as I'm not aware of any similar problems with 2.7, particularly when this addresses 2.7.3.rc3? |
The latest message from the reporter was at 2013-08-25: 6 years ago. I don't think that we will be able to continue to investigate the issue, so I close it as "out of date". |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: