Yes, the general rule was to actually understand what the error means, and if that didn't solve the problem, where it occurred and how did the thing get in the erroneous state (the thing called "debugging").