On Wed, Oct 5, 2011 at 1:49 PM, Alex Pyattaev <alex.pyatt...@gmail.com>wrote:
> 1. Switch to linux. It helps. > Not funny. 2. To get a meaningful error log try to run the pypy from terminal. To do > copy-paste you will need 3-rd party terminal, i.e. power shell. Then you'll > be > able to copy the error messages. Without them it is pretty much impossible > to > identify the problem. > I am running PyPy from terminal, bash provided by msys. The error still comes up in a dialog and the shell contains only the output from `nose` up to the failure, with no word on the failure. 3. Another option is to use debugger to run the suite step-by-step and see > what happens. > I'll give that a try. > > Choose your poison. > Alex. > On Wednesday 05 October 2011 13:44:14 Ram Rachum wrote: > > Hey guys, > > > > I upgraded to PyPy 1.6 on my 2 Windows XP 32 bit machines. It crashes on > > both system when running the GarlicSim test suite. > > > > It shows a Windows error dialog saying "pypy.exe has encountered a > problem > > and needs to close. We are sorry for the inconvenience." and giving this > > data: > > > > AppName: pypy.exe AppVer: 0.0.0.0 ModName: kernel32.dll > > ModVer: 5.1.2600.5512 Offset: 00040b0d > > > > > > I can also open a dialog with a lot of data on the error (don't know how > > useful it is) but Windows won't let me Ctrl-C it. > > > > > > What can I do? > > > > > > Thanks, > > Ram. > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > http://mail.python.org/mailman/listinfo/pypy-dev >
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
