Skip to content

Commit 1bb30aa

Browse files
committed
Fix parse_print_final_cbc dump when arguments is used
Currently the byte code start is incorrectly set when a non-strict arguments object is present, and a random memory area is dumped as byte code. JerryScript-DCO-1.0-Signed-off-by: Zoltan Herczeg zherczeg.u-szeged@partner.samsung.com
1 parent 86ecc81 commit 1bb30aa

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

jerry-core/parser/js/js-parser.c

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1228,10 +1228,6 @@ parse_print_final_cbc (ecma_compiled_code_t *compiled_code_p, /**< compiled code
12281228
}
12291229

12301230
byte_code_start_p += (unsigned int) (literal_end - register_end) * sizeof (ecma_value_t);
1231-
if (JERRY_UNLIKELY (compiled_code_p->status_flags & CBC_CODE_FLAGS_NON_STRICT_ARGUMENTS_NEEDED))
1232-
{
1233-
byte_code_start_p += argument_end * sizeof (ecma_value_t);
1234-
}
12351231

12361232
byte_code_end_p = byte_code_start_p + length;
12371233
byte_code_p = byte_code_start_p;

0 commit comments

Comments
 (0)