leftibot 85b8e7c0c8
Fix #633: [Bug] Stack-overflow due to infinite recursion in user-defined operator (string interpolation) (#700)
* Fix #633: Bound ChaiScript call stack to prevent native stack overflow

Recursive user-defined operators (e.g. a `string::/=` whose body calls
itself through string interpolation) drove the AST evaluator into
unbounded native recursion and crashed the host process with SIGSEGV.
The dispatcher now refuses to enter a new function frame once
`Stack_Holder::call_depth` reaches `chaiscript::max_call_depth`
(default 256, overridable via the `CHAISCRIPT_MAX_CALL_DEPTH` macro)
and throws the new `chaiscript::exception::stack_overflow_error`
instead, letting both ChaiScript-level `try`/`catch` and C++ hosts
recover from runaway recursion.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Address review: tighten max_call_depth on MSVC Debug

Windows MSVC Debug builds crashed unit.recursion_depth_protection.chai
with SEGFAULT before the depth check could fire. Windows defaults to a
1 MiB thread stack and Debug builds emit much larger per-frame native
stack usage (no inlining, /RTC, buffer security checks), so 256 nested
ChaiScript calls overflow the native stack long before the dispatcher
reaches max_call_depth. Linux/macOS and MSVC Release pass at 256.

Pick a tighter default (32) only for the MSVC + _DEBUG configuration
that needs it, leaving every other build at the original 256, and shrink
the count_down recursion in the regression test so the bounded path
stays well below every platform's default.

Requested by @lefticus in PR #700 review.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Address review: use CHAISCRIPT_DEBUG instead of _DEBUG

Switch CHAISCRIPT_DEBUG from a true/false definition to 1/0 so it can
be used in preprocessor #if expressions, then reuse it for the MSVC
Debug guard around CHAISCRIPT_MAX_CALL_DEPTH instead of testing the
compiler-private _DEBUG macro directly. The C++ debug_build constant
keeps its bool value through implicit conversion.

Requested by @lefticus in PR #700 review.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Address review: restore CHAISCRIPT_DEBUG to true/false for stronger typing

C++ preserves the true/false keywords in #if directives ([cpp.cond]),
so the MSVC Debug guard around CHAISCRIPT_MAX_CALL_DEPTH still works
without weakening the macro to integer 1/0.

Requested by @lefticus in PR #700 review.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: leftibot <leftibot@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-02 11:38:01 -06:00
.github Fix #690: Apply clang-format consistently with CI (#691) 2026-04-17 18:45:41 -06:00
cmake Enable warnings as errors (#694) 2026-04-28 20:11:15 -06:00
contrib Remove outdated vim support 2017-11-30 10:19:56 -07:00
emscripten Fix #693: Add Emscripten/embind bindings for get_state / set_state (needed for playground state reset) (#699) 2026-05-02 11:04:52 -06:00
grammar Fix #677: Add strong typedefs (#680) 2026-04-15 14:48:49 -06:00
include/chaiscript Fix #633: [Bug] Stack-overflow due to infinite recursion in user-defined operator (string interpolation) (#700) 2026-05-02 11:38:01 -06:00
performance_tests change .clang-format and reformat code with clang-format 11 2021-05-24 10:44:15 +02:00
samples Enable warnings as errors (#694) 2026-04-28 20:11:15 -06:00
src Enable warnings as errors (#694) 2026-04-28 20:11:15 -06:00
static_libs change .clang-format and reformat code with clang-format 11 2021-05-24 10:44:15 +02:00
unittests Fix #633: [Bug] Stack-overflow due to infinite recursion in user-defined operator (string interpolation) (#700) 2026-05-02 11:38:01 -06:00
.buckconfig * Added Buck build 2017-03-08 19:47:07 +00:00
.clang-format Fix #690: Apply clang-format consistently with CI (#691) 2026-04-17 18:45:41 -06:00
.decent_ci-Linux.yaml Remove g++ 4.8 from builds 2016-03-10 14:06:43 -07:00
.decent_ci-MacOS.yaml Move debug over to windows build 2016-03-05 12:04:30 -07:00
.decent_ci-Windows.yaml Merge branch 'develop' into update_travis_toolchain 2016-03-05 21:12:14 -07:00
.decent_ci.yaml Fix results location 2014-09-13 23:11:17 -06:00
.gitignore Add /build to .gitignore (#614) 2023-10-08 17:18:49 -04:00
.travis.yml Ci fix after moving to cpp17 (#455) 2018-10-20 08:50:08 -06:00
biicode.conf Update biicode and get master updated to v5.6.0 2015-03-19 20:03:12 -06:00
BUCK * Added Buckaroo.pm package 2017-07-21 11:09:53 +01:00
buckaroo.json * Added Buckaroo.pm package 2017-07-21 11:09:53 +01:00
cheatsheet.md Fix #116: Add set_file_reader callback for custom file loading (#683) 2026-04-15 16:25:09 -06:00
CMakeLists.txt Fix #693: Add Emscripten/embind bindings for get_state / set_state (needed for playground state reset) (#699) 2026-05-02 11:04:52 -06:00
description.txt Get cpack working for source and deb distribtions. Still need to check nsis and rpm 2010-03-29 15:32:20 +00:00
DesignGoals.md Create DesignGoals.md 2016-06-28 10:34:30 -06:00
Doxyfile.in Fix Doxygen configuration 2015-01-06 13:35:52 -07:00
LICENSE license: Restore Jonathan Turner copyright 2021-05-24 16:09:20 -04:00
license.txt license: Restore Jonathan Turner copyright 2021-05-24 16:09:20 -04:00
readme.md Fix #628: Grammar railroad diagram (#673) 2026-04-14 10:59:48 -06:00
releasenotes.md Fix #116: Add set_file_reader callback for custom file loading (#683) 2026-04-15 16:25:09 -06:00
supporters.md Create supporters.md 2016-03-05 18:32:44 -07:00

Master Status: Linux Build Status Windows Build status codecov.io

Develop Status: Linux Build Status Windows Build status codecov.io

ChaiScript

http://www.chaiscript.com

(c) 2009-2012 Jonathan Turner (c) 2009-2017 Jason Turner

Release under the BSD license, see "license.txt" for details.

Introduction

Gitter

ChaiScript is one of the only embedded scripting language designed from the ground up to directly target C++ and take advantage of modern C++ development techniques, working with the developer how they would expect it to work. Being a native C++ application, it has some advantages over existing embedded scripting languages:

  1. It uses a header-only approach, which makes it easy to integrate with existing projects.
  2. It maintains type safety between your C++ application and the user scripts.
  3. It supports a variety of C++ techniques including callbacks, overloaded functions, class methods, and stl containers.

Requirements

ChaiScript requires a C++17 compiler to build with support for variadic templates. It has been tested with gcc 7 and clang 6 (with libcxx).

Installation using vcpkg

You can download and install ChaiScript using the vcpkg dependency manager:

git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh
./vcpkg integrate install
vcpkg install chaiscript

The ChaiScript port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please create an issue or pull request on the vcpkg repository.

Usage

  • Add the ChaiScript include directory to your project's header search path
  • Add #include <chaiscript/chaiscript.hpp> to your source file
  • Instantiate the ChaiScript engine in your application. For example, create a new engine with the name chai like so: chaiscript::ChaiScript chai
  • The default behavior is to load the ChaiScript standard library from a loadable module. A second option is to compile the library into your code, see below for an example.

Once instantiated, the engine is ready to start running ChaiScript source. You have two main options for processing ChaiScript source: a line at a time using chai.eval(string) and a file at a time using chai.eval_file(fname)

To make functions in your C++ code visible to scripts, they must be registered with the scripting engine. To do so, call add:

chai.add(chaiscript::fun(&my_function), "my_function_name");

Once registered the function will be visible to scripts as "my_function_name"

Examples

ChaiScript is similar to ECMAScript (aka JavaScript(tm)), but with some modifications to make it easier to use. For usage examples see the "samples" directory, and for more in-depth look at the language, the unit tests in the "unittests" directory cover the most ground.

For examples of how to register parts of your C++ application, see "example.cpp" in the "samples" directory. Example.cpp is verbose and shows every possible way of working with the library. For further documentation generate the doxygen documentation in the build folder or see the website http://www.chaiscript.com.

Grammar

A formal EBNF grammar for ChaiScript is available in grammar/chaiscript.ebnf. To view it as a railroad diagram, paste the grammar into mingodad's railroad diagram generator or bottlecaps.de/rr.

The shortest complete example possible follows:

/// main.cpp

#include <chaiscript/chaiscript.hpp>

double function(int i, double j)
{
  return i * j;
}

int main()
{
  chaiscript::ChaiScript chai;
  chai.add(chaiscript::fun(&function), "function");

  double d = chai.eval<double>("function(3, 4.75);");
}