<div dir="ltr"><div class="gmail_quote">On Wed, Oct 5, 2011 at 2:23 PM, Alex Pyattaev <span dir="ltr"><<a href="mailto:alex.pyattaev@gmail.com">alex.pyattaev@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Generally, any binary-level debugger such as gdb or MSVC should work with<br>
pypy. At the very least you will find which operation crashed.<br></blockquote><div><br></div><div>As I said to Amaury, I don't know how to use those... Python is the only language I program in. </div><div><br></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If it is something really specific, for example<br>
sin/log/sign, it might be quite easy to map it back to python code. If it is<br>
not, it will be nearly impossible to find the original source line (at least<br>
I've failed when I tried).<br>
<br>
Another option is to edit the sources of the test suite adding print<br>
statements incrementally until you spot the place where it crashes. It is a<br>
slow, but very reliable way. That is of course if it is a particular segment<br>
of python code that crashes it.<br></blockquote><div><br></div><div>I'll try, thanks.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Also, could you send your exact environtment specs? I'll try to replicate it<br>
on a VM and see if it crashes for me too. I have an XP VM somewhere.<br></blockquote><div><br></div><div>What specs do you mean? It's just the recent PyPy 1.6 on a Windows XP SP3 32 bit machine with minimal packages installed. (distribute, pip, nosetests.)</div>
<div><br></div><div>Let me know if you need any more data.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
PS: Sorry for my stupid joke about switching to linux. It was meant to cheer<br>
you up a bit.<br></blockquote><div><br></div><div>Forgiven :)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Alex.<br>
<div><div></div><div class="h5"><br>
On Wednesday 05 October 2011 14:18:08 Ram Rachum wrote:<br>
> On Wed, Oct 5, 2011 at 2:11 PM, Amaury Forgeot d'Arc<br>
<<a href="mailto:amauryfa@gmail.com">amauryfa@gmail.com</a>>wrote:<br>
> > 2011/10/5 Ram Rachum <<a href="mailto:ram@rachum.com">ram@rachum.com</a>>:<br>
> > > I have hundreds of tests, and PyPy fails before a single one begins.<br>
> > > It<br>
> > > seems that PyPy crashes somewhere in nose's initialization.<br>
> > > Isn't there a way to find the last Python line run before the crash<br>
> ><br>
> > without<br>
> ><br>
> > > stepping with a finer granularity every time?<br>
> ><br>
> > Not without a debugger, I'm afraid<br>
> ><br>
> > --<br>
> > Amaury Forgeot d'Arc<br>
><br>
> How do I run the Nose test suite on Pypy with a debugger? I usually use Wing<br>
> IDE, but it doesn't support PyPy. I'm also aware of Nose's `--pdb` flag<br>
> which drops you into the debugger after an error, but it doesn't work here<br>
> because this crash seems to be happening at a lower level. So I don't know<br>
> how to start this in a debugger.<br>
><br>
><br>
> Ram.<br>
</div></div><div><div></div><div class="h5">_______________________________________________<br>
pypy-dev mailing list<br>
<a href="mailto:pypy-dev@python.org">pypy-dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/pypy-dev" target="_blank">http://mail.python.org/mailman/listinfo/pypy-dev</a><br>
</div></div></blockquote></div><br></div>