[lldb-dev] XCode build failing

2017-08-01 Thread Vadim Macagon via lldb-dev 

Hi,

My changes in r309664 (https://reviews.llvm.org/D35881) broke the XCode 
build, I'm guessing because I didn't update the XCode project(s) to 
reference these new files:


include/lldb/API/SBProcessInfo.h
trunk/scripts/interface/SBProcessInfo.i
source/API/SBProcessInfo.cpp

Could someone please update the XCode project(s)? I don't have a Mac.


Thanks,

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

Re: [lldb-dev] MI command for connecting remote target

2016-09-22 Thread Vadim Macagon via lldb-dev 
You need to specify the executable to debug before attempting to connect 
to the remote machine:



lldb-mi --interpreter


-file-exec-and-symbols local/path/to/executable
-target-select remote host:port

Note that the file-exec-and-symbols command has some non-standard 
extensions in LLDB-MI that are documented in 



On 23/09/2016 7:07 AM, Chunseok Lee via lldb-dev wrote:
However, when I try the same thing with lldb-mi, I cannot connect to 
remote target as follows:


--- host log 
twoflower@js1-desktop ~/local-hello> lldb-mi-3.8.1
(gdb)
-target-select remote 10.113.62.251:1234 
^error,msg="Command 'target-select'. Current SBTarget is invalid"
(gdb)

--  remote log --
twoflower@twoflower ~/remote-hello> lldb-server-3.8 p --listen "*:1234"

The remote side seems not to receive any msg at all.
I am not sure that it is proper use for -target-select command.

BR,
Chunseok Lee




On 23/09/2016 7:07 AM, Chunseok Lee via lldb-dev wrote:

Is there any MI command for connecting remote target ?

Using platform and target command with lldb, It works fine as follows:

-host log--
twoflower@js1-desktop ~/local-hello> ls
a.out*  hello.cpp
twoflower@js1-desktop ~/local-hello> lldb-3.8.1
(lldb) platform select remote-linux
  Platform: remote-linux
 Connected: no
(lldb) platform connect connect://10.113.62.251:1234 


  Platform: remote-linux
Triple: x86_64-*-linux-gnu
OS Version: 3.19.0 (3.19.0-32-generic)
Kernel: #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015
  Hostname: twoflower
 Connected: yes
WorkingDir: /home/twoflower/remote-hello
(lldb) target create -r /home/twoflower/remote-hello/a.out a.out
Current executable set to 'a.out' (x86_64).
(lldb) b main
Breakpoint 1: where = a.out`main, address = 0x0040052d
(lldb) r
Process 14524 launched: 
'/home/twoflower/.lldb/module_cache/remote-linux/.cache/BB42308F-4677-5DC0-AFC2-097CDFE91A83-3612C4F8/a.out' 
(x86_64)

Process 14524 stopped
* thread #1: tid = 14524, 0x0040052d a.out`main, name = 
'a.out', stop reason = breakpoint 1.1

frame #0: 0x0040052d a.out`main
a.out`main:
->  0x40052d <+0>: pushq  %rbp
0x40052e <+1>: movq   %rsp, %rbp
0x400531 <+4>: movl   $0x4005d4, %edi   ; imm = 0x4005D4
0x400536 <+9>: movl   $0x0, %eax
(lldb) c
Process 14524 resuming
Process 14524 exited with status = 0 (0x)
(lldb) q
twoflower@js1-desktop ~/local-hello>

--remote log ---
twoflower@twoflower ~/remote-hello> ls
a.out*  hello.cpp
twoflower@twoflower ~/remote-hello> lldb-server-3.8 p --listen "*:1234"
Connection established.
error: lost connection
lldb-server exiting...

--

However, when I try the same thing with lldb-mi, I cannot connect to 
remote target as follows:


--- host log 
twoflower@js1-desktop ~/local-hello> lldb-mi-3.8.1
(gdb)
-target-select remote 10.113.62.251:1234 
^error,msg="Command 'target-select'. Current SBTarget is invalid"
(gdb)

--  remote log --
twoflower@twoflower ~/remote-hello> lldb-server-3.8 p --listen "*:1234"

The remote side seems not to receive any msg at all.
I am not sure that it is proper use for -target-select command.

BR,
Chunseok Lee

--
Where Do We come from? What Are We? Where Are We Going?


___
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

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

2015-10-05 Thread Vadim Macagon via lldb-dev 
A couple of fixes to the Python/LLDB Windows build process were 
committed on Oct 1st, I suggest you try building a more recent revision 
(especially if setting CMAKE_BUILD_TYPE to Debug as suggested by Zach 
fixes your issue).


On 6/10/2015 3:15 AM, Zachary Turner via lldb-dev wrote:

Are you using -DCMAKE_BUILD_TYPE=Debug when you generate CMake?

On Mon, Oct 5, 2015 at 1:14 PM kwadwo amankwa > wrote:


Thanks for the response ,  sorry for the delay. As a matter of
fact I actually got rid of the system python and installed my
custom version.  I do suspect it is a linking problem though. When
I build liblldb.dll it always loads python27.dll instead of
python27_d.dll. Do you happen to know where the python27 lib is
specified as an input library because the project properties in
liblldb does not specify it . however the linker complains if I
don't specify the lib directory in 'additional directories' and
when I do it always links to the python27lib. I grepped the whole
build directory and two files SystemInitializer.obj and
LLDBWrapPython.obj seem to contain /DEFAULTLIB:python27.lib. Do
you have an idea of what is causing the compiler to do this ?


On 05/10/15 19:13, Zachary Turner wrote:

Ahh, I thought you were doing this from inside LLDB.  There are a
couple of problems:

1) You might be running with the system Python, not the custom
Python you built with VS2013.  What is the value of `sys.executable`?
2) Even if you are running your own Python, the regular Python
appears to be in your `sys.path`.  You will need to unset
PYTHONPATH and PYTHONHOME from pointing to your system Python. 
PYTHONHOME should point to your custom Python, and PYTHONPATH

should point to the `lib\site-packages` directory that I
mentioned earlier in your build directory.



On Mon, Oct 5, 2015 at 11:06 AM kwadwo amankwa
mailto:q...@lunarblack.com>> wrote:

here it is;

C:\Users\redbandit\Documents\GitHub\pygui>python
Python 2.7.10 (default, Sep 18 2015, 02:35:59) [MSC v.1800 64
bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more
information.
>>> import sys
>>> sys.path
['', 'C:\\Python27\\Lib',
'C:\\Users\\redbandit\\llvm\\build\\Debug\\lib\\site-packages\\lldb',
'C:\\Users\\redbandit\\llvm\\build\\tools\\lldb\\scripts',
'C:\\Users\\redbandi t\\Documents\\GitHub\\pygui',
'C:\\Python27\\python27.zip', 'C:\\Python27\\DLLs',
'C:\\Python27\\lib\\plat-win', 'C:\\Python27\\lib\\lib-tk',
'C:\\Python27', 'C:\\Python27\\li b\\site-packages']
>>> import lldb
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named embedded_interpreter
>>> lldb.__file__
'C:\\Users\\redbandit\\llvm\\build\\tools\\lldb\\scripts\\lldb.pyc'

>>> sys.path
['C:/Users/redbandit/llvm/build/Debug/lib/site-packages/lldb', 
'C:/Users/redbandit/llvm/build/Debug/lib/site-packages/lib/site-packages',
'', 'C:\\Python27\\Lib', 'C:\\Users\\
redbandit\\llvm\\build\\Debug\\lib\\site-packages\\lldb',
'C:\\Users\\redbandit\\llvm\\build\\tools\\lldb\\scripts',
'C:\\Users\\redbandit\\Documents\\GitHub\\pygui', 'C:\\Pyt
hon27\\python27.zip', 'C:\\Python27\\DLLs',
'C:\\Python27\\lib\\plat-win', 'C:\\Python27\\lib\\lib-tk',
'C:\\Python27', 'C:\\Python27\\lib\\site-packages', '.']


On 05/10/15 18:48, Zachary Turner wrote:

Can you run the followign commands and paste the output?

>>> import sys
>>> sys.path
['D:/src/llvmbuild/ninja/bin',
'D:/src/llvmbuild/ninja/lib/site-packages',
'D:\\src\\llvmbuild\\ninja\\bin\\python27_d.zip',
'C:\\Python27_LLDB\\x86\\DLLs',
'C:\\Python27_LLDB\\x86\\lib',
'C:\\Python27_LLDB\\x86\\lib\\plat-win',
'C:\\Python27_LLDB\\x86\\lib\\lib-tk',
'D:\\src\\llvmbuild\\ninja\\bin'
, 'C:\\Python27_LLDB\\x86',
'C:\\Python27_LLDB\\x86\\lib\\site-packages', '.']
>>> import lldb
>>> lldb.__file__
'D:/src/llvmbuild/ninja/lib/site-packages\\lldb\\__init__.pyc'
>>> sys.path
['D:/src/llvmbuild/ninja/bin',
'D:/src/llvmbuild/ninja/lib/site-packages',
'D:\\src\\llvmbuild\\ninja\\bin\\python27_d.zip',
'C:\\Python27_LLDB\\x86\\DLLs',
'C:\\Python27_LLDB\\x86\\lib',
'C:\\Python27_LLDB\\x86\\lib\\plat-win',
'C:\\Python27_LLDB\\x86\\lib\\lib-tk',
'D:\\src\\llvmbuild\\ninja\\bin'
, 'C:\\Python27_LLDB\\x86',
'C:\\Python27_LLDB\\x86\\lib\\site-packages', '.']
>>>

and also make sure that in the same folder as your
_lldb_d.pyd, there is an embedded_interpreter.py?

On Mon, Oct 5, 2015 at 9:14 AM kwadwo amankwa