[Python-Dev] core out of select.so

Guido van Rossum guido@python.org
Wed, 17 Apr 2002 16:11:32 -0400

> On Wed, Apr 17, 2002 at 12:34:15PM -0700, Geoff Gerrietts wrote:
> >My backtraces appear to vary in quality (not sure why) -- sometimes I
> >get all the symbols I expect, sometimes I get no symbols at all. The
> >best traceback I have at the moment (though I
> Please create a bug report on SourceForge for it (or send a traceback
> or two to me privately, and I can file a bug report).
> If the tracebacks show that the segfault is occurring at different
> places in the C code, it's possible that some extension has a
> refcounting bug or is overwriting malloc'ed memory.  The actual crash
> would then come later in different code that isn't actually buggy.
> --amk

Since he mentioned select.so, I'm curious if he might be overflowing
the thread stack.  That might cause a corrupt stack.  There's no way
to get a reliable C trace once the stack has been corrupted.  You need
more info before it makes sense to submit this to SF.

--Guido van Rossum (home page: http://www.python.org/~guido/)