The `__future__` we relied on is now, where the 3 specific things are
all included [since Python 3.0](https://docs.python.org/3/library/__future__.html):
* absolute_import
* print_function
* unicode_literals
* division
These import statements are no-ops and are no longer necessary.
This test broke when we switched to the swift-4.2-branch of Clang/LLVM.
It seems to be a problem with LLDB's CreateTargetWithFileAndArch() API
(rdar://problem/39960149). In the meantime, since this script does not
really need to specify the architecture, we can work around the problem
by using CreateTarget(). That's simpler anyway.
rdar://problem/38181372
When ldd returns a list of libraries, the binary reflects the name
that the library is known at at link time. However, it may be a
symlink to a different filename on the system, which can confuse
generated tools that capture the image name from a process map.
Handle both cases so that the logical name and the file name is handled.
Follows advise from python's man page:
'Note that there is internal buffering in xread-lines(), readlines() and file-object iterators ("for line in sys.stdin") which is not influenced by this option. To work around this, you will want to use "sys.stdin.readline()" inside a "while 1:" loop.'
