ladybird/Userland/Libraries/LibJS/Bytecode/Instruction.cpp
Andreas Kling 1c06111cbd LibJS: Add file & line number to bytecode VM stack traces :^)
This works by adding source start/end offset to every bytecode
instruction. In the future we can make this more efficient by keeping
a map of bytecode ranges to source ranges in the Executable instead,
but let's just get traces working first.

Co-Authored-By: Andrew Kaster <akaster@serenityos.org>
2023-09-02 15:37:53 +02:00

45 lines
1.1 KiB
C++

/*
* Copyright (c) 2021, Andreas Kling <kling@serenityos.org>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
#include <LibJS/Bytecode/Executable.h>
#include <LibJS/Bytecode/Instruction.h>
#include <LibJS/Bytecode/Op.h>
namespace JS::Bytecode {
void Instruction::destroy(Instruction& instruction)
{
#define __BYTECODE_OP(op) \
case Type::op: \
static_cast<Op::op&>(instruction).~op(); \
return;
switch (instruction.type()) {
ENUMERATE_BYTECODE_OPS(__BYTECODE_OP)
default:
VERIFY_NOT_REACHED();
}
#undef __BYTECODE_OP
}
UnrealizedSourceRange InstructionStreamIterator::source_range() const
{
VERIFY(m_executable);
auto record = dereference().source_record();
return {
.source_code = m_executable->source_code,
.start_offset = record.source_start_offset,
.end_offset = record.source_end_offset,
};
}
RefPtr<SourceCode> InstructionStreamIterator::source_code() const
{
return m_executable ? m_executable->source_code.ptr() : nullptr;
}
}