<div dir="ltr"><div class="gmail_quote">On Thu, Oct 6, 2011 at 10:13 AM, Amaury Forgeot d'Arc <span dir="ltr"><<a href="mailto:amauryfa@gmail.com">amauryfa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
2011/10/5 Martin Kretschmar <<a href="mailto:kretschmar-martin@t-online.de">kretschmar-martin@t-online.de</a>>:<br>
<div class="im">> Microsofts free WinDbg (<a href="http://en.wikipedia.org/wiki/WinDbg" target="_blank">http://en.wikipedia.org/wiki/WinDbg</a>) can also attach<br>
> to running processes.<br>
<br>
</div>A release build of pypy contains no debug information<br>
Believe me, a debugger won't show anything useful.<br>
<br>
It's already difficult enough in a debug build (because of the generated C code)<br>
and almost impossible when JIT code is involved, except maybe for Armin :-)<br>
<br>
A reproducible (short) test case would be really appreciated.<br>
<div><div></div><div class="h5"><br>
--<br>
Amaury Forgeot d'Arc<br>
</div></div></blockquote></div><br><div><br></div><div>Hey guys,</div><div><br></div><div>I've managed to produce a VM that shows the bug.</div><div><br></div><div>You can download it here:</div><div><br></div><div><a href="http://dl.dropbox.com/u/1927707/VM%20for%20debugging%20PyPy.rar">http://dl.dropbox.com/u/1927707/VM%20for%20debugging%20PyPy.rar</a></div>
<div><br></div><div>It's a VMWare Virtual Machine, and it weighs 2 GB compressed.</div><div><br></div><div>Once you fire up the VM, there are short instructions in a text file on the desktop to making PyPy crash.</div>
<div><br></div><div>Will anyone have time to try that?</div><div><br></div><div><br></div><div>Thanks,</div><div>Ram.</div></div>