Desc<"If true, inject local variables explicitly into the expression text. This will fix symbol resolution when there are name collisions between ivars and local variables. But it can make expressions run much more slowly.">;
}
letDefinition="target"in{
defDefaultArch:Property<"default-arch","Arch">,
Global,
DefaultStringValue<"">,
Desc<"Default architecture to choose, when there's a choice.">;
Desc<"Skip function prologues when setting breakpoints by name.">;
defSourceMap:Property<"source-map","PathMap">,
DefaultStringValue<"">,
Desc<"Source path remappings are used to track the change of location between a source file when built, and where it exists on the current system. It consists of an array of duples, the first element of each duple is some part (starting at the root) of the path to the file when it was built, and the second is where the remainder of the original build hierarchy is rooted on the local system. Each element of the array is checked in order and the first one that results in a match wins.">;
Desc<"Consult the platform module avoid list when setting non-module specific breakpoints.">;
defArg0:Property<"arg0","String">,
DefaultStringValue<"">,
Desc<"The first argument passed to the program in the argument array which can be different from the executable itself.">;
defRunArgs:Property<"run-args","Args">,
DefaultStringValue<"">,
Desc<"A list containing all the arguments to be passed to the executable when it is run. Note that this does NOT include the argv[0] which is in target.arg0.">;
defEnvVars:Property<"env-vars","Dictionary">,
DefaultUnsignedValue<16>,
Desc<"A list of all the environment variables to be passed to the executable's environment, and their values.">;
defInheritEnv:Property<"inherit-env","Boolean">,
DefaultTrue,
Desc<"Inherit the environment from the process that is running LLDB.">;
defInputPath:Property<"input-path","FileSpec">,
DefaultStringValue<"">,
Desc<"The file/path to be used by the executable program for reading its standard input.">;
defOutputPath:Property<"output-path","FileSpec">,
DefaultStringValue<"">,
Desc<"The file/path to be used by the executable program for writing its standard output.">;
defErrorPath:Property<"error-path","FileSpec">,
DefaultStringValue<"">,
Desc<"The file/path to be used by the executable program for writing its standard error.">;
Desc<"The strategy to use when settings breakpoints by file and line. Breakpoint locations can end up being inlined by the compiler, so that a compile unit 'a.c' might contain an inlined function from another source file. Usually this is limited to breakpoint locations from inlined functions from header or other include files, or more accurately non-implementation source files. Sometimes code might #include implementation files and cause inlined breakpoint locations in inlined implementation files. Always checking for inlined breakpoint locations can be expensive (memory and time), so if you have a project with many headers and find that setting breakpoints is slow, then you can change this setting to headers. This setting allows you to control exactly which strategy is used when setting file and line breakpoints.">;
Desc<"Loading modules from memory can be slow as reading the symbol tables and other data can take a long time depending on your connection to the debug target. This setting helps users control how much information gets loaded when loading modules from memory.'complete' is the default value for this setting which will load all sections and symbols by reading them from memory (slowest, most accurate). 'partial' will load sections and attempt to find function bounds without downloading the symbol table (faster, still accurate, missing symbol names). 'minimal' is the fastest setting and will load section data with no symbols, but should rarely be used as stack frames in these memory regions will be inaccurate and not provide any context (fastest). ">;
Desc<"Expressions that crash will show up in crash logs if the host system supports executable specific crash log strings and this setting is set to true.">;
Desc<"A list containing extra commands understood by the particular process plugin used. For instance, to turn on debugserver logging set this to 'QSetLogging:bitmask=LOG_DEFAULT;'">;
Desc<"If true, when step-in/step-out/step-over leave the current frame, they will continue to step out till they come to a function with debug information. Passing a frame argument to step-out will override this option.">;
