Specific .lldbinit project in current working directory not readable by Xcode

I want to configure project-specific .lldbinit files so that "everything" is versioned and easily configured on new computers. However, it seems to me that I can only read the ~ / .lldbinit file , not the ~ / git / project / .lldbinit files.

LLDB management will say:

lldb will read settings / aliases / commands from three files at startup, if they exist.

First , he will read the batch file ~ / .lldbinit-debugger. If you're using the lldb command line interface, this is ~ / .lldbinit-lldb. if you use lldb inside a GUI debugger such as Xcode, it will be ~ / .lldbinit- Xcode. This is a useful place to set parameters that you only want to apply when using the lldb command interpreter.

Second , ~ / .lldbinit is read.

Third , the .lldbinit file in the current working directory (where lldb is running).

So my question is: how do I configure Xcode or a project to use the "third" option, that is, read the .lldbinit file from the current working directory? How can I check or change what Xcode is "current working directory"?

+6
source share
2 answers

There is currently an Xcode plugin for downloading a specific .lldbinit project at https://github.com/alloy/lldb-is-it-not

0
source

This is the working directory in which you start any process that loads the LLDB structure. Xcode does not have a useful working directory (it was / the last time I looked), so you cannot use the cwd version.

The solution for specific Xcode-specific lcb projects that will work in many cases is to put a symbolic breakpoint on the main one, set it to continue automatically, and then put the necessary settings into the breakpoint commands of this breakpoint.

It would be great if Xcode had some user interface to specify lldbinit files for specific purposes.

0
source

Source: https://habr.com/ru/post/985658/


All Articles