Commit 24e47234 authored by David Renshaw's avatar David Renshaw

Edit error message for the case where copyPointer() hits a FAR pointer.

The existing error message suggests this case can only arise if there is a
a bug in the library. However, malformed input can trigger the error too.
In particular, the error gets thrown when a non-double far pointer resolves
to another far pointer.
parent 01f6d5e4
......@@ -1872,7 +1872,7 @@ struct WireHelpers {
}
case WirePointer::FAR:
KJ_FAIL_ASSERT("Far pointer should have been handled above.") {
KJ_FAIL_ASSERT("Unexpected FAR pointer.") {
goto useDefault;
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment