[pypy-dev] Fw: Crash!

[Ben.Young at risk.sungard.com]

Sorry about replying to myself, but I must be going blind as the crash is 
still being caused by an exception being thrown. Weird that the tests 
don't pick this up!

Cheers,
Ben 


pypy-dev-bounces at codespeak.net wrote on 23/09/2005 13:05:13:

> Further to my previous mail, current check seems to crash much more 
often 
> now:
> 
> $ ./pypy-c.exe
> debug: entry point starting
> debug:  argv -> c:\Documents and 
> Settings\YoungB\dist\pypy\translator\goal\pypy-c.exe
> debug: importing code
> debug: calling code.interact()
> Python 2.4.1 (pypy 0.7.1 build) on win32
> Type "help", "copyright", "credits" or "license" for more information.
> (InteractiveConsole)
> >>>> import test
> >>>> test.rpython.main(100)
> 
> -> Segfault
> 
> Cheers,
> Ben
> 
> ----- Forwarded by Ben Young/Infinity on 23/09/2005 13:05 -----
> 
> Ben Young/Infinity wrote on 22/09/2005 12:47:14:
> 
> > Hi Everyone,
> > 
> > Current checkout, compiled pypy (windows as usual):
> > 
> > $ ./pypy-c.exe
> > debug: entry point starting
> > debug:  argv -> c:\Documents and 
> > Settings\YoungB\dist\pypy\translator\goal\pypy-c.exe
> > debug: importing code
> > debug: calling code.interact()
> > Python 2.4.1 (pypy 0.7.1 build) on win32
> > Type "help", "copyright", "credits" or "license" for more information.
> > (InteractiveConsole)
> > >>>> fe
> > 
> > -> Segfault
> > 
> > Appears to be a problem throwing exceptions.
> > 
> > On another point, I notice that when lists of pointers are resized 
> > lots of incref/decrefs happen when all that really needs to happen 
> > is a move operation (or even a memcpy of the whole block)? Also, 
> > could all lists of pointers share the same c representation, with 
> > casts from void*?
> > 
> > Cheers,
> > Ben
> _______________________________________________
> pypy-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/pypy-dev
> 
>