Carlos Ribeiro <carribe...@gmail.com> added the comment:
Thanks for investigating!
I'll keep watching. I'm currently developing a small Django app, and the
crash happened during one of the automatic reloads that the development
server do whenever a source code file changes. The problem is that I
probably ran through the same procedure several hundred times over the past
few weeks, but the bug happened only *once*. Seems like a nasty bug. I
*suspect* it may be thread related, a racing condition or something like it.
(and yes, I'm using a regular build, not a debug build).
Also note that I use Python since 1998 and never, in the past 12 years, I
had a dump like this.
As for this ticket, it seems like a nasty and elusive bug; I _feel_ that we
may never see the same bug again, _but_ other people may encounter similar
situations, and we can then try to correlate them to find the cause. If I
don't manage to reproduce it over the next few days we may close it but keep
it in the tracker, until someone else hits it again.
Best regards,
Carlos Ribeiro
On Sun, Mar 21, 2010 at 16:29, Alexander Belopolsky
<rep...@bugs.python.org>wrote:
>
> Alexander Belopolsky <alexander.belopol...@gmail.com> added the comment:
>
> Clearly not enough information, but I have a few observations:
>
> 1. Clearly the crash occurs on exit (in Py_Finalize) during a module
> cleanup. (Unfortunately it looks like a non-debug build of Python was used
> so figuring out which module is involved may be hard.
>
> 2. Memory map suggests that the crash is very late in python finalization.
> Note that only two python modules are still mapped: mxDateTime and
> _hashlib. However the memmap seems incomplete.
>
> Try to reproduce the crash with a debug build of python (configure
> --with-pydebug). The debug build may also crash sooner and more reliably.
>
> ----------
> nosy: +Alexander.Belopolsky
>
> _______________________________________
> Python tracker <rep...@bugs.python.org>
> <http://bugs.python.org/issue8176>
> _______________________________________
>
----------
Added file: http://bugs.python.org/file16615/unnamed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8176>
_______________________________________
Thanks for investigating!<br><br>I'll keep watching. I'm currently
developing a small Django app, and the crash happened during one of the
automatic reloads that the development server do whenever a source code file
changes. The problem is that I probably ran through the same procedure several
hundred times over the past few weeks, but the bug happened only *once*. Seems
like a nasty bug. I *suspect* it may be thread related, a racing condition or
something like it. (and yes, I'm using a regular build, not a debug
build).<br>
<br>Also note that I use Python since 1998 and never, in the past 12 years, I
had a dump like this.<br><br>As for this ticket, it seems like a nasty and
elusive bug; I _feel_ that we may never see the same bug again, _but_ other
people may encounter similar situations, and we can then try to correlate them
to find the cause. If I don't manage to reproduce it over the next few days
we may close it but keep it in the tracker, until someone else hits it
again.<br>
<br>Best regards,<br><br>Carlos Ribeiro<br><br><br><div class="gmail_quote">On
Sun, Mar 21, 2010 at 16:29, Alexander Belopolsky <span dir="ltr"><<a
href="mailto:rep...@bugs.python.org";>rep...@bugs.python.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left:
1px solid rgb(204, 204, 204); padding-left: 1ex;"><br>
Alexander Belopolsky <<a
href="mailto:alexander.belopol...@gmail.com";>alexander.belopol...@gmail.com</a>>
added the comment:<br>
<br>
Clearly not enough information, but I have a few observations:<br>
<br>
1. Clearly the crash occurs on exit (in Py_Finalize) during a module cleanup.
 (Unfortunately it looks like a non-debug build of Python was used so figuring
out which module is involved may be hard.<br>
<br>
2. Memory map suggests that the crash is very late in python finalization.
 Note that only two python modules are still mapped: mxDateTime and _hashlib.
 However the memmap seems incomplete.<br>
<br>
Try to reproduce the crash with a debug build of python (configure
--with-pydebug). Â The debug build may also crash sooner and more reliably.<br>
<br>
----------<br>
nosy: +Alexander.Belopolsky<br>
<div><div></div><div class="h5"><br>
_______________________________________<br>
Python tracker <<a
href="mailto:rep...@bugs.python.org";>rep...@bugs.python.org</a>><br>
<<a href="http://bugs.python.org/issue8176";
target="_blank">http://bugs.python.org/issue8176</a>><br>
_______________________________________<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Carlos
Ribeiro<br>Consultoria em Projetos<br>twitter: <a
href="http://twitter.com/carribeiro";>http://twitter.com/carribeiro</a><br>blog:
<a
href="http://rascunhosrotos.blogspot.com";>http://rascunhosrotos.blogspot.com</a><br>
mail: <a href="mailto:carribe...@gmail.com";>carribe...@gmail.com</a><br>
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
