> That Python path bug is fixed. But I'll check the other paths that can be > requested using Host::GetLLDBPath and try to get them all correct using only > relative paths (which seems the best choice. That should work for in-tree and > installed builds using makefiles.
Nevertheless, lldb still hogs 100% CPU and does nothing on my machine. -- Regards, Konstantin _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
