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
Hi,
Running into a problem where closing the TTY window on OS X while on a
breakpoint using LLDB-MI does not allow the SIGHUP to be passed through to the
debuggee. I had to add the following call to get the debuggee to terminate when
closing the window if LLDB-MI was not in a break state.
proc
omm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
-Original Message-
From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Pierson
Lee (PIE) via lldb-dev
Sent: Monday, July 11, 2016 1:33 PM
T
main
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
-Original Message-
From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Pierson
Lee (PIE) via lldb-dev
Sent: Monday, J
flag.
But also lldb-mi should probably just ignore this flag.
Jim
> On Jul 8, 2016, at 5:58 PM, Pierson Lee (PIE) via lldb-dev
> wrote:
>
> Hi,
>
> I’m trying to use -break-insert and the -f flag for it.
>
> I noticed in MICmdCmdBreak.cpp , in CmICmdCmdBre
Hi,
I'm trying to use -break-insert and the -f flag for it.
I noticed in MICmdCmdBreak.cpp , in CmICmdCmdBreakInsert::ParseArgs() that the
-f has a required parameter.
m_setCmdArgs.Add(new
CMICmdArgValOptionShort(m_constStrArgNamedPendinfBrkPt, false, true,
Hi
I'm building LLDB v3.8 on my osx mac using Unix Makefiles and when I go and
test it with the built debugserver, I get the following errors when passing
"run":
error: process exited with status -1 (unable to attach)
I verified that attaching to a process also doesn't work.
Is there a known
r251082.
Please fill a bug report on
llvm.org/bugs<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fllvm.org%2fbugs&data=01%7c01%7cPierson.Lee%40microsoft.com%7c49f011e335c8436a02fc08d398e739a5%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=8EJ1X0DsyxwIj%2fqcqpJCk2sC0s9k
Hi,
I've built lldb on tag release_38 (3.8.1) with the flag LLDB_DISABLE_PYTHON=1
and I'm getting the below error when running lldb-mi:
MI: Error: Driver. LLDB Debugger.
MI: Error: Driver Manager. Driver 'Machine Interface Driver Version: 1.0.0.9'
(ID:'MIDriver') initialise failed. Driver. LLDB
