I seem to be able to pretty reliably produce the following:
Exception- InternalError: indirect - invalid constant address raised while compiling
Exception- InternalError: indirect - invalid constant address raised while compiling
Unfortunately, it takes hours to get there...
Switching to --gcthreads=1 may have fixed another error we were having, relating to unwarranted pointer-equality tests.
Michael
On 21/02/14 22:30, David Matthews wrote:
Hi, I'm aware of a number of assertion failures that seem to occur intermittently. This is one of the ones on my list. I suspect they are all symptoms of the same bug but I have never been able to narrow it down or reproduce it. It does seem to occur when the memory management is under heavy load.
Thanks for reporting it and if anyone manages to reproduce it more consistently I would be very interested.
Regards, David
On 20/02/2014 14:21, Ond?ej Kun?ar wrote:
Hi! In the past couple of months I've gotten a crash of PolyML always with the same error message. I cannot reproduce the problem reliably but because it has already happened, let say, six times in the past three months, I am reporting the problem here:
Unofficial version of Isabelle/HOL (unidentified repository version) poly: gc_mark_phase.cpp:432: virtual void MTGCProcessMarkPointers::ScanAddressesInObject(PolyObject*, POLYUNSIGNED): Assertion `baseAddr > (PolyWord*)obj && baseAddr < ((PolyWord*)obj)+length' failed.
This refers to any changeset in the past three months.
Best, Ondrej _______________________________________________ isabelle-dev mailing list isabelle-dev at in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
isabelle-dev mailing list isabelle-dev at in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev