nnovation Center, Inc.
> > The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
> >
> >
> > -Original Message-----
> > From: Greg Clayton [mailto:gclay...@apple.com]
> > Sent: Monday, March 21, 2016 1:01 PM
> >
.
>>
>> --
>> Qualcomm Innovation Center, Inc.
>> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
>> Linux Foundation Collaborative Project
>>
>>
>> -Original Message-
>> From: Greg Clayton [mailto:gclay...@appl
omm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
> -Original Message-
> From: Greg Clayton [mailto:gclay...@apple.com]
> Sent: Monday, March 21, 2016 1:01 PM
> To:
arch 21, 2016 1:01 PM
To: Ted Woodward
Cc: LLDB
Subject: Re: [lldb-dev] Windows lldb prompt issue
All input and output are handled by IOHandler subclasses. There is a stack of
them. When you start LLDB you get one thing on the IOHandler stack: the LLDB
command interpreter:
IOHandlers:
[0] IO
All input and output are handled by IOHandler subclasses. There is a stack of
them. When you start LLDB you get one thing on the IOHandler stack: the LLDB
command interpreter:
IOHandlers:
[0] IOHandlerEditline for command interpreter
If you type "script" at the LLDB command prompt, the command
This has been a longstanding issue which I just haven't been able to
prioritize over things such as PDB support, minidump support, test fixes,
etc. There's various thread synchronization stuff that happens between the
IOHandler thread and the debugger thread, and I guess there's a race
condition o
I run lldb on Windows and Linux, launching my gdb-server based Hexagon
simulator automatically on a process launch. On Windows I'm seeing the
(lldb) prompt before the stop message, and no prompt after. On Linux I see
the prompt after.
Windows:
Current executable set to 'u:\lldb_test\factwin' (
