[Python-Dev] Crash in new "trashcan" mechanism.

[Christian Tismer]

Vladimir Marangozov wrote:
> 
> Christian Tismer wrote:
> >
> > Vladimir Marangozov wrote:
> > >
> > > Maybe unrelated, but this code does not handle the case when
> > > PyList_Append fails. If it fails, the object needs to be deallocated
> > > as usual. Looking at the macros, I don't see how you can do that
> > > because Py_TRASHCAN_SAFE_END, which calls the above function,
> > > occurs after the finalization code...
> >
> > Yes, it does not handle this case for the following reasons:
> > ...
> 
> Not enough good reasons to segfault. I suggest you move the
> call to _PyTrash_deposit_object in TRASHCAN_BEGIN and invert
> the condition there.

Sorry, I don't see what you are suggesting, I'm distracted.
Maybe you want to submit a patch, and a few more words
on what you mean and why you prefer to core dump
with stack overflow?

I'm busy seeking a bug in the core, not in that ridiculous code.
Somewhere is a real bug, probably the one which I was
seeking many time before, when I got weird crashes in the small
block heap of Windows. It was never solved, and never clear if
it was Python or Windows memory management.
Maybe we just found another entrance to this.
It smells so very familiar: many many small tuples and we crash.

busy-ly y'rs - chris

-- 
Christian Tismer             :^)   <mailto:tismer@appliedbiometrics.com>
Applied Biometrics GmbH      :     Have a break! Take a ride on Python's
Kaunstr. 26                  :    *Starship* http://starship.python.net
14163 Berlin                 :     PGP key -> http://wwwkeys.pgp.net
PGP Fingerprint       E182 71C7 1A9D 66E9 9D15  D3CC D4D7 93E2 1FAE F6DF
     where do you want to jump today?   http://www.stackless.com