[Python-Dev] pdb segfaults in 2.5 trunk? (original) (raw)
Neal Norwitz nnorwitz at gmail.com
Mon Apr 10 22:44:10 CEST 2006
- Previous message: [Python-Dev] pdb segfaults in 2.5 trunk?
- Next message: [Python-Dev] pdb segfaults in 2.5 trunk?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 4/10/06, Phillip J. Eby <pje at telecommunity.com> wrote:
It appears the problem is an object/mem mismatch: both PyOSReadline in pgenmain.c, and PyOSStdioReadline use PyObjectMALLOC, but bltinmodule.c is freeing the pointer with PyMemFREE.
This (Readline using PyObject) was due to my recent change to fix Guido's problem last night. I didn't realize anything seeped out. All calls to PyOS_StdioReadline would need to be updated. I can do that tonight. Hmm, that means this will be an API change. I wonder if I should revert my fix and just deal with a second alloc and copy of the data to fix Guido's original problem.
n
- Previous message: [Python-Dev] pdb segfaults in 2.5 trunk?
- Next message: [Python-Dev] pdb segfaults in 2.5 trunk?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]