[Docs] Correct description of lldbinit behavior

Jim pointed out that "every time somebody has touched the documentation
on startup files they have stated that we source the application one and
then the global one, even though in actual fact we’ve never done that."

Indeed, when we read the application specific .lldbinit file, the global
one is not read. This patch updates the man page to reflect that.
This commit is contained in:
Jonas Devlieghere 2020-05-28 13:06:44 -07:00
parent 51401a676c
commit ac1dc1336a
1 changed files with 11 additions and 7 deletions

View File

@ -303,13 +303,17 @@ CONFIGURATION FILES
-------------------
:program:`lldb` reads things like settings, aliases and commands from the
.lldbinit file. First, it will read the application specific init file whose
name is ~/.lldbinit followed by a "-" and the name of the current program. This
would be ~/.lldbinit-lldb for the command line :program:`lldb` and
~/.lldbinit-Xcode for Xcode. Secondly, the global ~/.lldbinit will be read.
Finally, :program:`lldb` will look for an .lldbinit file in the current working
directory. For security reasons, :program:`lldb` will print a warning and not
source this file by default. This behavior can be changed by changing the
.lldbinit file.
First, it will read the application specific init file whose name is
~/.lldbinit followed by a "-" and the name of the current program. This would
be ~/.lldbinit-lldb for the command line :program:`lldb` and ~/.lldbinit-Xcode
for Xcode. If there is no application specific init file, the global
~/.lldbinit is read.
Secondly, it will look for an .lldbinit file in the current working directory.
For security reasons, :program:`lldb` will print a warning and not source this
file by default. This behavior can be changed by changing the
target.load-cwd-lldbinit setting.
To always load the .lldbinit file in the current working directory, add the