On Wednesday February 04 2015 23:44:25 André Pönitz wrote: > The solution is to start LLDB, and use the Python it links to implicitly > by using the LLDB 'script' command, instead of hoping that the system Python > is the right one.
In fact, are you really sure?? I just did this on OS X: %> lldb (lldb) script Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D. >>> sys.executable '/opt/local/bin/python' >>> sys.version '2.7.5 (default, Mar 9 2014, 22:15:05) \n[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)]' That's MacPorts' python, not the system one, and the one that's first in my path but which caused errors debugging in Qt Creator before I realised I was tapping into the wrong Python ... R. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
