On Saturday 01 December 2007 10:49:24 Will Coleda wrote: > I don't normally build on windows, but tried today to verify some code for > kid51; started by doing a basic build against trunk: > > winxp, visual studio 2005, r23314 > > Build ends with: > > ..\..\parrot.exe ..\..\compilers\tge\tgc.pir --output=POST\Grammar_gen.p > ir POST\Grammar.tg > Parrot VM: PANIC: Null vtable used! > C file src\pmc.c, line 199d > Parrot file (not available), line (not available) > > We highly suggest you notify the Parrot team if you have not been working > on Parrot. Use parrotbug (located in parrot's root directory) or send an > e-mail to [EMAIL PROTECTED] > Include the entire text of this error message and the text of the script > that > generated the error. If you've made any modifications to Parrot, please > describe them as well. > > Version : 0.5.0-devel > Configured : Sat Nov 24 23:48:48 2007 GMT > Architecture: i386-MSWin32 > JIT Capable : Yes > Interp Flags: 0 > Exceptions : (missing from core) > > Dumping Core... > Sorry, coredump is not yet implemented for this platform. > > NMAKE : fatal error U1077: '..\..\parrot.exe' : return code '0x1' > Stop. > NMAKE : fatal error U1077: 'C:\Perl\bin\perl.exe' : return code '0x2' > Stop.
A backtrace would be nice. We've also invalidated bytecode a few times recently, so if you didn't do a realclean first, please try that to see if it clears up. -- c
