maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lldb/source/Interpreter/InterpreterProperties.td

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
2.1 KiB
TableGen
Raw Normal View History

[TableGen] Move interpreter properties into a separate file (NFC) With the plugins having their own tablgen file, it makes sense to split off the interpreter properties as well. llvm-svn: 367138
2019-07-27 02:14:04 +08:00
include "../../include/lldb/Core/PropertiesBase.td"
[lldb] Also include the array definition in Properties.inc Right now our Properties.inc only generates the initializer for the options list but not the array declaration boilerplate around it. As the array definition is identical for all arrays, we might as well also let the Properties.inc generate it alongside the initializers. Unfortunately we cannot do the same for enums, as there's this magic ePropertyExperimental, which needs to come at the end to be interpreted correctly. Hopefully we can get rid of this in the future and do the same for the property enums. Differential revision: https://reviews.llvm.org/D65353 llvm-svn: 367238
2019-07-30 00:41:30 +08:00
let Definition = "interpreter" in {
[TableGen] Move interpreter properties into a separate file (NFC) With the plugins having their own tablgen file, it makes sense to split off the interpreter properties as well. llvm-svn: 367138
2019-07-27 02:14:04 +08:00
def ExpandRegexAliases: Property<"expand-regex-aliases", "Boolean">,
Global,
DefaultFalse,
Desc<"If true, regular expression alias commands will show the expanded command that will be executed. This can be used to debug new regular expression alias commands.">;
def PromptOnQuit: Property<"prompt-on-quit", "Boolean">,
Global,
DefaultTrue,
Desc<"If true, LLDB will prompt you before quitting if there are any live processes being debugged. If false, LLDB will quit without asking in any case.">;
[lldb/interpreter] Add ability to save lldb session to a file This patch introduce a new feature that allows the users to save their debugging session's transcript (commands + outputs) to a file. It differs from the reproducers since it doesn't require to capture a session preemptively and replay the reproducer file in lldb. The user can choose the save its session manually using the session save command or automatically by setting the interpreter.save-session-on-quit on their init file. To do so, the patch adds a Stream object to the CommandInterpreter that will hold the input command from the IOHandler and the CommandReturnObject output and error. This way, that stream object accumulates passively all the interactions throughout the session and will save them to disk on demand. The user can specify a file path where the session's transcript will be saved. However, it is optional, and when it is not provided, lldb will create a temporary file name according to the session date and time. rdar://63347792 Differential Revision: https://reviews.llvm.org/D82155 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2020-07-21 22:29:16 +08:00
def SaveSessionOnQuit: Property<"save-session-on-quit", "Boolean">,
Global,
DefaultFalse,
Desc<"If true, LLDB will save the session's transcripts before quitting.">;
[lldb/Interpreter] Add setting to set session transcript save directory This patch introduces a new interpreter setting `interpreter.save-session-directory` so the user can specify a directory where the session transcripts will be saved. If not set, the session transcript are saved on a temporary file. rdar://72902842 Differential Revision: https://reviews.llvm.org/D105030 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-06-29 01:41:26 +08:00
def SaveSessionDirectory: Property<"save-session-directory", "FileSpec">,
DefaultStringValue<"">,
Desc<"A path where LLDB will save the session's transcripts. This is particularly useful when you can't set the session file, for example when using `save-session-on-quit`.">;
[TableGen] Move interpreter properties into a separate file (NFC) With the plugins having their own tablgen file, it makes sense to split off the interpreter properties as well. llvm-svn: 367138
2019-07-27 02:14:04 +08:00
def StopCmdSourceOnError: Property<"stop-command-source-on-error", "Boolean">,
Global,
DefaultTrue,
Desc<"If true, LLDB will stop running a 'command source' script upon encountering an error.">;
def SpaceReplPrompts: Property<"space-repl-prompts", "Boolean">,
Global,
DefaultFalse,
Desc<"If true, blank lines will be printed between between REPL submissions.">;
def EchoCommands: Property<"echo-commands", "Boolean">,
Global,
DefaultTrue,
Desc<"If true, commands will be echoed before they are evaluated.">;
def EchoCommentCommands: Property<"echo-comment-commands", "Boolean">,
Global,
DefaultTrue,
Desc<"If true, commands will be echoed even if they are pure comment lines.">;
[lldb/Interpreter] Add `interpreter.repeat-previous-command` setting This patch introduces a new interpreter setting to prevent LLDB from re-executing the previous command when passing an empty command. This can be very useful when performing actions that requires a long time to complete. To preserve the original behaviour, the setting defaults to `true`. rdar://74983516 Differential Revision: https://reviews.llvm.org/D97999 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-03-06 02:30:48 +08:00
def RepeatPreviousCommand: Property<"repeat-previous-command", "Boolean">,
Global,
DefaultTrue,
Desc<"If true, LLDB will repeat the previous command if no command was passed to the interpreter. If false, LLDB won't repeat the previous command but only return a new prompt.">;
[TableGen] Move interpreter properties into a separate file (NFC) With the plugins having their own tablgen file, it makes sense to split off the interpreter properties as well. llvm-svn: 367138
2019-07-27 02:14:04 +08:00
}