On Mon, Aug 15, 2016 at 2:36 AM, Pavel Labath via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> I've sampled the python code from the llvm repository, and it seems to
> be using a mixture of 4-, 2-, and even 8- character indent, with 4
> being the most prevalent. So, I think we can safely stay with
I am trying to run LLDB from the 3.8.0 release on a Debian 8 system.
However, LLDB hangs during attach:
$ lldb /bin/ls
(lldb) target create "/bin/ls"
Current executable set to '/bin/ls' (x86_64).
(lldb) r
At which point it hangs. From another window:
$ ps -eLf|grep djones
djones 32218 7418 32
r246756 has a fix, if you are comfortable applying it. It's a large patch.
In theory it should back-port but I have not tried it.
The API gap from 3.7.1 to 3.8 is quite minimal, so you should be able to
get your applications running with 3.8 rather easily if they are running on
3.7.1 already.
O
I'm trying out the release candidate(?) as follows:
svn co http://llvm.org/svn/llvm-project/llvm/branches/release_38 llvm
svn co http://llvm.org/svn/llvm-project/cfe/branches/release_38 cfe
svn co http://llvm.org/svn/llvm-project/lldb/branches/release_38 lldb
cd llvm/tools
ln -s ../../cfe clang
l
I have some code which worked under LLVM+LLDB 3.6.0 which runs as follows:
its purpose is to run some code, and print a backtrace if the code
segfaults. My approach was:
- fork
- the child runs the main part of the program.
- the parent creates a debugger and attaches to the child. The child is
con
