github
/
duktape
mirror of https://github.com/svaarala/duktape.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6556 Commits
65 Branches
60 Tags
84 MiB
Tree: e609103c03
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e609103c03'
${ noResults }
duktape/config/config-options/DUK_USE_DEBUGGER_TRANSPORT_...

16 lines
495 B
Raw Normal View History

Genconfig metadata and headers first version
9 years ago
define: DUK_USE_DEBUGGER_TRANSPORT_TORTURE
Config metadata improvements
9 years ago
feature_enables: DUK_OPT_DEBUGGER_TRANSPORT_TORTURE
Genconfig metadata and headers first version
9 years ago
introduced: 1.2.0
Don't "require" debugger support for debugger opts DUK_USE_DEBUGGER_THROW_NOTIFY default is "true". If the option "requires" DUK_USE_DEBUGGER_SUPPORT (which defaults to "false") the option configuraiton would be inconsistent and rejected by default. Remove the "required" metadata for debugger options: the options don't really require debugger support. Instead, if debugger support is disabled, the debugger config options are just ignored without causing a build error.
9 years ago
# Option is ignored unless debugger support is enabled.
#requires:
# - DUK_USE_DEBUGGER_SUPPORT
Genconfig metadata and headers first version
9 years ago
default: false
tags:
- debugger
- development
Config option changes for refzero torture
9 years ago
- torture
Genconfig metadata and headers first version
9 years ago
description: >
Development time option: force debugger transport torture. Concretely this
now causes Duktape to read/write debug protocol data in 1-byte increments,
which stresses message parsing and transport code.