freenode/#sbcl - IRC Chatlog
Search
22:51:48
earl-ducaine
A while ago, an application I was working on started consistently generating an "Unhandled memory fault at #x5" error in SBCL. I traced it back to an application error, it was trying to modify a hashtable while a maphash was in progress on the same table.
22:51:52
earl-ducaine
My question is whether I should create a bug report or is that within the range of acceptable undefined behavior in SBCL for that type of program error.
23:08:42
earl-ducaine
i.e. before that commit, SBCL was more forgiving with respect to that type of in progress modification.
23:16:35
scymtym
if i recall correctly, the "more forgiving" behavior (which actually was silent corruption) was changed to either an AVER or an ASSERT. so the memory fault is indeed unexpected
2:24:35
adlai
earl-ducaine: if that error was consistent, then there is an interesting aspect to the report