Re: [lldb-dev] Process not launching in example python script from lldb documentation

2017-01-03 Thread Роман Попов via lldb-dev
Ok, I've figured it out: looks like install script was broken:

I build and install lldb using:
cmake ../llvm
make
make DESTDIR=$CLANG_INSTALL_PATH install

LLDB installed this way is not working.

But when I use python package directly from
build_dir//lib/python2.7/site-packages it is working fine:

$ ./python_example.py
Creating a target for './a.out'
SBBreakpoint: id = 1, name = 'main', module = a.out, locations = 1
SBProcess: pid = 5853, state = stopped, threads = 1, executable = a.out
thread #1: tid = 5853, 0x0040081a a.out`main(argc=1,
argv=0x7ffed229c738) at main.cpp:3, name = 'a.out', stop reason =
breakpoint 1.1
...




2017-01-02 23:52 GMT-08:00 Роман Попов :

> Hello,
> Looks like last python example from http://lldb.llvm.org/pyth
> on-reference.html is not working (using the lldb.py module in python).
> For some reason process is not launching in debugger.
>
> I'm using clang++ and lldb from llvm trunk on Ubuntu 14.04 x64:
>
> $ cat main.cpp
> #include 
> int main (int argc, char **argv) {
>   std::cout << "Hello world \n";
>   return 0;
> }
>
>
> $ clang++ -g main.cpp
> $ ./python_example.py
>
>  Creating a target for './a.out'
>  SBBreakpoint: id = 1, name = 'main', module = a.out, locations = 1
>  SBProcess: pid = 0, state = launching, threads = 0, executable = a.out
>
> Process state is "launching", but should be "eStateStopped" according to
> comments in source code.
>
>
> -Roman
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [RFC] Delete the "testcases" symlink

2017-01-03 Thread Pavel Labath via lldb-dev
On 15 December 2016 at 19:11, Zachary Turner via lldb-dev
 wrote:
> It's definitely possible to (at worst) shorten the path if we say we don't
> care about supporting other languages (i'm fine saying that for now unless
> someone comes along with a serious committment to support and maintaining
> other bindings).  So we could drop packages/Python for example.


We were contemplating some sort of a Java binding for lldb, but that
isn't going to happen any time soon, so you don't have to hold a place
open for other languages because of us.

Happy new year,
pl
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Changes in the install of lldb ?

2017-01-03 Thread Chris Bieneman via lldb-dev
I pushed a fix that should resolve this in r290934.

Sorry for the breakage!
-Chris

> On Dec 25, 2016, at 10:18 AM, Sylvestre Ledru via lldb-dev 
>  wrote:
> 
> Hello
> 
> Recently (couple of weeks), the generation of the apt.llvm.org packages
> is failing because some lldb binaries are sometime no longer generated
> 
> For example, on debian unstable, the following files are no longer
> generated:
> 
> usr/lib/llvm-4.0/bin/lldb-server
> usr/lib/llvm-4.0/bin/lldb-argdumper
> 
> Does is ring a bell to anyone?
> Thanks,
> Sylvestre
> PS: please cc me
> 
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev