steve
/
factor
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

vm: We don't want ambiguity for which print triggered on a gc error. Differentiate the error messages.

db4
Doug Coleman 2014-12-03 20:36:13 -06:00
parent 5dc7cce253
commit 875d2421df
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
vm/gc.cpp
View File

@ -97,7 +97,7 @@ void factor_vm::start_gc_again() {
default:
/* Nothing else should fail mid-collection due to insufficient
space in the target generation. */
critical_error("Bad GC op", current_gc->op);
critical_error("in start_gc_again, bad GC op", current_gc->op);
break;
}
@ -163,7 +163,7 @@ void factor_vm::gc(gc_op op, cell requested_size, bool trace_contexts_p) {
collect_growing_heap(requested_size, trace_contexts_p);
break;
default:
critical_error("Bad GC op", current_gc->op);
critical_error("in gc, bad GC op", current_gc->op);
break;
}