Currently our PDBASTParser and SymbolFilePDB can only work on Windows
because it relies on a builtin Windows library.
In LLVM now we have full ability to read, parse, and interpret the contents
of PDB files at the byte level. There are two approaches to getting this
working in LLDB.
1) Re-implem
To clarify, #1 is saying to re-implement the API **in LLVM** so that LLDB
transparently just works with no code changes. While #2 is saying to
re-implement the plugin **in LLDB** to not use that API at all, and instead
use the low-level API that parses records directly from the file.
On Tue, Oct
Hi,
I'm using lldb-mi to debug on OS X and I'm trying to redirect the debuggee
output to a tty, but it seems like it wants to use the lldb-launcher
(Darwin-debug) add on and open a terminal instead.
Is there a way to have the debuggee stdin/stdout redirection be sent to a tty
of my specificati
The way to do this in the MI interface is with the command: inferior-tty-set.
Unfortunately, that command isn't implemented in the lldb-mi:
bool CMICmdCmdInferiorTtySet::Execute() {
// Do nothing
return MIstatus::success;
}
This should set the target.{input/output/error}-path to the tty it
