Skip to content

Add test environment for debugging with static snapshots enabled #2637

Open
@akosthekiss

Description

@akosthekiss

Recording a scenario from #2606

[A] failure was found when debugging IoT.js with static snapshots turned on, if an error was thrown an assertion failure was caused. The reason is the frame context's bytecode_header_p pointer was not a heap pointer. The jerry_debugger_breakpoint_hit function tries to set a compressed pointer which points to bytecode_header_p with the JMEM_CP_SET_NON_NULL_POINTER macro, which has an assertion that requires the above mentioned bytecode_header_p to be a heap pointer, which is obviously not.

[Creating a a JerryScript-only test environment is n]ot a trivial task. You need a unit test which creates such an environment, and you also need the python debugger to do debugging. Hence it needs a new infrastructure basically, where instead of a .js, a binary is run by the debugger tester driver.

Metadata

Metadata

Assignees

No one assigned

    Labels

    debuggerRelated to the debuggersnapshotRelated to the snapshot featuretestRelated to testing

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions