[lldb-dev] Where is lldb.py?

[Zachary Turner]

Interesting.  I had already made some progress towards this in my own
branch, so I'll have a look.

BTW, I'm not sure what your solution was regarding the missing python
modules, but the pexpect one in particualr is pretty trivial to fix.  Just
change it to subprocess.run() and remove the import of pexpect.


On Mon, Jun 23, 2014 at 5:09 PM, Deepak Panickal <deepak at codeplay.com>
wrote:

>  We have already ported the lldb.py generating scripts to Python for
> portability and got the API working in Windows and Linux.
> We can load an ELF file, dump symbols, do remote debugging etc.
> This work has been put into review sometime ago, so might need some
> updation.
>
> http://reviews.llvm.org/D2980 <http://llvm-reviews.chandlerc.com/D2980>
>
> We're planning to fix it up quite soon to match with the current tip.
>
> Thanks,
> Deepak
>
>
> On 23/06/2014 22:09, Zachary Turner wrote:
>
> I'm already volunteering, just want to make sure it's ok before I do the
> work :)
>
>  That being said, Greg mentions in an earlier message that it might not
> be possible because we wish to support a Python-less build.   Who uses this
> out of curiosity?  I don't think any Windows developers mind installing
> Python as a requirement.  It's also mentioned on the Building LLDB page (
> http://lldb.llvm.org/build.html) that Python is a dependency
>
>
> On Mon, Jun 23, 2014 at 2:07 PM, Todd Fiala <tfiala at google.com> wrote:
>
>> You can volunteer to write it more portably ;-)
>>
>>
>> On Mon, Jun 23, 2014 at 1:55 PM, Zachary Turner <zturner at google.com>
>> wrote:
>>
>>> Hmm, a shell script.  kind of a non-starter for Windows.  Any reason
>>> this can't be a python script?
>>>
>>>
>>> On Mon, Jun 23, 2014 at 1:52 PM, Greg Clayton <gclayton at apple.com>
>>> wrote:
>>>
>>>> It is generated by running swig with many options. See:
>>>>
>>>> lldb/scripts/build-swig-wrapper-classes.sh
>>>>
>>>>
>>>>
>>>> > On Jun 23, 2014, at 1:41 PM, Zachary Turner <zturner at google.com>
>>>> wrote:
>>>> >
>>>> > I'm trying to get the test suite into a working state on windows, or
>>>> at the very least get it to the point where it fails by saying that none of
>>>> the tests are supported on this platform.  I seem to be missing this file
>>>> lldb.py though.  Is it supposed to be in the tree, or is it generated
>>>> somehow?
>>>>  > _______________________________________________
>>>> > lldb-dev mailing list
>>>> > lldb-dev at cs.uiuc.edu
>>>> > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> lldb-dev mailing list
>>> lldb-dev at cs.uiuc.edu
>>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>>
>>>
>>
>>
>>   --
>>   Todd Fiala |  Software Engineer |  tfiala at google.com |  650-943-3180
>>
>
>
>
> _______________________________________________
> lldb-dev mailing listlldb-dev at cs.uiuc.eduhttp://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140623/d61916a6/attachment.html>