If a new read action hasn't had a chance to choose a valid reads-from or
reads-from-promise, it can have "no" value. This only occurs if we are
terminating an infeasible execution, where there were no valid reads to
read from.
This bug was triggering faults only for verbose printing, were we would
print the status of an incomplete read.
ASSERT(is_read());
if (reads_from)
return reads_from->get_write_value();
- return reads_from_promise->get_value();
+ else if (reads_from_promise)
+ return reads_from_promise->get_value();
+ return VALUE_NONE; /* Only for new actions with no reads-from */
}
/**