Fix and simplify invocation of noSuchMethod on ARM after the wrong number of

Fix and simplify invocation of noSuchMethod on ARM after the wrong number of
arguments is passed.
The frame of the wrong method (the one invoked with the wrong number of
arguments) is not left on the stack and therefore not visible in the stack trace
anymore, which is much cleaner, especially since the leftover frame was not
fully initialized.
Note: We should simplify this on other platforms as well.

R=zra@google.com

Committed: https://code.google.com/p/dart/source/detail?r=24475

[zra, 2013-06-26 16:13:19]

lgtm

Just to make sure, there will still be enough position information available in
the stack trace to identify the call that has too many arguments, right?

[regis, 2013-06-26 16:29:49]

On 2013/06/26 16:13:19, zra wrote:
> lgtm
> 
> Just to make sure, there will still be enough position information available
in
> the stack trace to identify the call that has too many arguments, right?

The removed position information was used to identify the leftover frame, which
is now gone.
I did not touch the position information related to the caller.

[regis, 2013-06-26 16:31:56]

Committed patchset #2 manually as r24475 (presubmit successful).