[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Changes by Terry J. Reedy : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Changes by SilentGhost : -- resolution: -> invalid stage: test needed -> committed/rejected ___ Python tracker ___ ___ Python-bugs-lis

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Ryan Kelly added the comment: Thanks for the help, I have tracked this down to a bug in PyCrypto. It was increfing an object once but decrefing it twice. Sorry for the noise. -- ___ Python tracker __

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Charles-Francois Natali added the comment: > The code that is segfaulting is using pycrypto and sqlite3, so it may be that > a bug in one of these is trampling on something. No idea how to investigate > any further. You could try valgrind: $ valgrind --tool=memcheck -o /tmp/output.log argu

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Ryan Kelly added the comment: attaching core dump from a freshly-compiled python 2.7.1 at with "-O0 -g" in CFLAGS. The code that is segfaulting is using pycrypto and sqlite3, so it may be that a bug in one of these is trampling on something. No idea how to investigate any further.

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Ryan Kelly added the comment: Please remind me how to obtain an appropriate coredump (as I said, it's been a *long* time...) Doing "print bp" shows an out-of-bounds address as for the original submitter. -- ___ Python tracker

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Charles-Francois Natali added the comment: Do you have a coredump ? It'd be curious to see this faulting address. I didn't notice the first time, but in the OP case the address is definitely wrong: 0xecc778b7 is above PAGE_OFFSET (0xc000 on x86), so unless he's using a kernel with a 4G/4G

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Ryan Kelly added the comment: Not sure if it's caused by the same thing, but I just got a segfault on the same line in my own program. Running python 2.7.1. I will try to dig out some more useful info but it's been a long time since I chased a segfault... -- nosy: +rfk status: pendi

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Terry J. Reedy added the comment: Is this reproducible? Has is occurred with 2.7 or 3.x? Or should be close this? -- nosy: +tjreedy status: open -> pending versions: +Python 2.7 -Python 2.5 ___ Python tracker _

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

Charles-Francois Natali added the comment: It was a long time ago, but: - I think the interpreter will never be able to catch all memory allocation errors, since because of overcommitting (which Linux does), you can very well get a segmentation fault even if the memory allocation routine (be i

[issue5091] Segfault in PyObject_Malloc(), address out of bounds

New submission from Christian Heimes : One of our application recently started to segfault in PyObject_Malloc(). The cause of the problem could be tracked down to an overflowing internal cache. However I was astonished that Python was segfaulting instead of raising a memory exception. I did some