[Python-Dev] Segfault

[Hrvoje Nikšić]

On Thu, 2007-08-23 at 11:57 -0700, Neal Norwitz wrote:
> > "allow threads" section that runs with the GIL released, file_close
> > might acquire the GIL and be running in parallel to this code.  If
> > file_close sets f_fp to NULL after the "if" condition evaluates, but
> > before the call to _portable_fseek completes, we still get a segfault.
> 
> However, the setting of f_fp to NULL happens with the GIL set, ie
> while only one thread is running.

I thought other "IO-bound" threads (the sections that "allow threads")
could also run in parallel.  Otherwise what is the point of
BEGIN_ALLOW_THREADS?