From: Daniel J. <dan...@gm...> - 2017-03-18 21:30:07
|
Which compiler version are you using? Did you upgrade it recently? Does it also crash when compiled without optimisations (-O0) ? Bruno Haible <br...@cl...> schrieb am Sa., 18. März 2017, 22:04: > Hi Don, > > > Could this be related to the MT problems? > > I was thinking that possibly the failure in MT might be due to > > choosing a different memory model than the one that was working > > before, and that we might find out more by extending your memory > > model test to try to build and run MT versions. > > For me, it crashes even without MT, and in different memory models: > > Linux/x86_64: > build-porting64-gcc-spvw_pure_blocks *** - APPLY: Too > few arguments for #<STANDARD-GENERIC-FUNCTION COMPUTE-SLOTS> > > Linux/arm: > build-porting32-gcc-spvw_pure_blocks/cbcstep3.log KO > Segmentation fault during streams tests > > FreeBSD/i386: > build-porting32-gcc-wide/cbcstep3.log KO > Signal 11 > > FreeBSD/x86_64: > build-porting64-gcc-generational_gc-multithread_gc/cbcstep3.log Crash in > steele7 tests > build-porting64-gcc-generational_gc-old_gc/cbcstep3.log Crash in > socket tests > build-porting64-gcc-safety0/cbcstep3.log Crash in > steele7 tests > build-porting64-gcc-safety0-optimized/cbcstep3.log Crash in > steele7 tests > > NetBSD/x86_64: > build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log > Segmentation fault during path tests > > OpenBSD/x86_64: > build-porting64-gcc-heapcodes/cbcstep3.log KO > Segmentation fault during number tests > build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log KO > Segmentation fault during number tests > build-porting64-gcc-heapcodes-spvw_pages/cbcstep3.log KO > Segmentation fault during number tests > build-porting64-gcc-one_free_bit_heapcodes/cbcstep3.log KO > Segmentation fault during number tests > > Bruno > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > clisp-devel mailing list > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clisp-devel > |