Opcode for out of gas inside a message call

Question

According to the Solidity documentation:

A require-style exception is generated in the following situations:

...

If you call a function via a message call but it does not finish properly (i.e. it runs out of gas, has no matching function, or throws an exception itself)

...

Internally, Solidity performs a revert operation (instruction 0xfd) for a require-style exception and executes an invalid operation (instruction 0xfe) to throw an assert-style exception.

However in this transaction an 0xfe opcode is performed (see step 1394) which is used for assert-style exceptions.

Is the documentation incorrect or the compiler doesn't follow the documentation?

Answer 1

If you look at the source code of the function withdrawTokens

function withdrawToken(address token, uint amount) {
  if (token==0) throw;
  if (tokens[token][msg.sender] < amount) throw;
  tokens[token][msg.sender] = safeSub(tokens[token][msg.sender], amount);
  if (!Token(token).transfer(msg.sender, amount)) throw;
  Withdraw(token, msg.sender, amount, tokens[token][msg.sender]);
}

It explicitely have a throw, and throw will generate 0xfe.

The contract was compiled with version v0.4.9, and require and assert are only available from v0.4.10.