[lldb-dev] multiple NameErrors on lldb startup, doesn't seem to affect lldb performance

[Peter Rowat via lldb-dev]

Here is what happens:


 prowat% lldb modTS
(lldb) target create "modTS"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python/lldb/__init__.py", line 98, in <module>
    import six
ImportError: No module named six
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
..
..
..  (at least 100 repetitions) ..
..
..
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Current executable set to 'modTS' (x86_64).
(lldb)

===============
Exactly the same output appears when lldb is started by:
==============
(lldb) process attach -n modTS

==================================
 prowat% lldb -v
lldb-902.0.79.7
  Swift-4.1
===============

This is a nuisance but LLDB is still usable.
 
====
OSX 10.13
Peter 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20180615/366d8591/attachment.html>