Generally, any binary-level debugger such as gdb or MSVC should work with pypy. At the very least you will find which operation crashed.
If it is something really specific, for example sin/log/sign, it might be quite easy to map it back to python code. If it is not, it will be nearly impossible to find the original source line (at least I've failed when I tried). Another option is to edit the sources of the test suite adding print statements incrementally until you spot the place where it crashes. It is a slow, but very reliable way. That is of course if it is a particular segment of python code that crashes it. Also, could you send your exact environtment specs? I'll try to replicate it on a VM and see if it crashes for me too. I have an XP VM somewhere. PS: Sorry for my stupid joke about switching to linux. It was meant to cheer you up a bit. Alex. On Wednesday 05 October 2011 14:18:08 Ram Rachum wrote: > On Wed, Oct 5, 2011 at 2:11 PM, Amaury Forgeot d'Arc <amaur...@gmail.com>wrote: > > 2011/10/5 Ram Rachum <r...@rachum.com>: > > > I have hundreds of tests, and PyPy fails before a single one begins. > > > It > > > seems that PyPy crashes somewhere in nose's initialization. > > > Isn't there a way to find the last Python line run before the crash > > > > without > > > > > stepping with a finer granularity every time? > > > > Not without a debugger, I'm afraid > > > > -- > > Amaury Forgeot d'Arc > > How do I run the Nose test suite on Pypy with a debugger? I usually use Wing > IDE, but it doesn't support PyPy. I'm also aware of Nose's `--pdb` flag > which drops you into the debugger after an error, but it doesn't work here > because this crash seems to be happening at a lower level. So I don't know > how to start this in a debugger. > > > Ram. _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
