6 commits

Author	SHA1	Message	Date
Linus Groh	8e84ca6b16	LibJS: Don't apply arguments object hack to global execution context ... Checking for the existence of a call frame is not enough to check if we're in a function call, as the global execution context is a regular call frame as well. Found by OSS-Fuzz, where simply accessing "arguments" in the global scope would crash due to call_frame().callee being an empty value (https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32115).	2021-03-16 18:48:25 +01:00
Andreas Kling	8062fc711c	LibJS: Add arguments.callee to our hack arguments object ... arguments.callee refers to the currently executing function.	2021-03-15 21:20:33 +01:00
Jean-Baptiste Boric	6f668ca3a4	LibJS: Fix crash due to AST node tracking inside call stack	2021-03-01 22:27:27 +01:00
Jean-Baptiste Boric	6172cb3599	LibJS: Keep track of current AST node inside the call stack	2021-03-01 11:14:36 +01:00
Andreas Kling	5d180d1f99	Everywhere: Rename ASSERT => VERIFY ... (...and ASSERT_NOT_REACHED => VERIFY_NOT_REACHED) Since all of these checks are done in release builds as well, let's rename them to VERIFY to prevent confusion, as everyone is used to assertions being compiled out in release. We can introduce a new ASSERT macro that is specifically for debug checks, but I'm doing this wholesale conversion first since we've accumulated thousands of these already, and it's not immediately obvious which ones are suitable for ASSERT.	2021-02-23 20:56:54 +01:00
Andreas Kling	13d7c09125	Libraries: Move to Userland/Libraries/	2021-01-12 12:17:46 +01:00

Renamed from Libraries/LibJS/Runtime/VM.cpp (Browse further)