wasm-interp crashes with no error message when the wrong number of arguments is given.

For example, when running the identity function:

```wasm
(module
  (func (export "id") (param i32) (result i32) (local.get 0))
)
```

```
% wasm-interp identity.wasm --run-export=id
[1]    102759 segmentation fault (core dumped)  wasm-interp identity.wasm --run-export=id

% wasm-interp identity.wasm --run-export=id --argument=i32:7
id(i32:7) => i32:7

% wasm-interp identity.wasm --run-export=id --argument=i32:7 --argument=i32:8
[1]    102811 abort (core dumped)  wasm-interp identity.wasm --run-export=id --argument=i32:7 --argument=i32:8
```

Version:
```
% wasm-interp --version
1.0.33
```
wasm-interp crashes when wrong number of arguments passed
This is a GitHub Issue
repo:wabt
owner:WebAssembly
Title : wasm-interp crashes when wrong number of arguments passed
Issue date:

--- start body ---
wasm-interp crashes with no error message when the wrong number of arguments is given.

For example, when running the identity function:

```wasm
(module
  (func (export "id") (param i32) (result i32) (local.get 0))
)
```

```
% wasm-interp identity.wasm --run-export=id
[1]    102759 segmentation fault (core dumped)  wasm-interp identity.wasm --run-export=id

% wasm-interp identity.wasm --run-export=id --argument=i32:7
id(i32:7) => i32:7

% wasm-interp identity.wasm --run-export=id --argument=i32:7 --argument=i32:8
[1]    102811 abort (core dumped)  wasm-interp identity.wasm --run-export=id --argument=i32:7 --argument=i32:8
```

Version:
```
% wasm-interp --version
1.0.33
```
--- end body ---

The wasm-interp tool in version 1.0.33 crashes with a segmentation fault when an incorrect number of arguments is passed to a function. This indicates a potential vulnerability where improper input handling can lead to application crashes, which could be exploited by an attacker to cause denial of service.