Re: [lldb-dev] [Bug 27020] New: "command alias r run" causes an assert

2016-03-21 Thread Enrico Granata via lldb-dev
> On Mar 21, 2016, at 2:27 PM, via lldb-dev wrote: > > Bug ID27020 > Summary "command alias r run" causes an assert > Product lldb > Version unspecified > Hardware PC > OSWindows NT > StatusNEW >

[lldb-dev] [Bug 27020] New: "command alias r run" causes an assert

2016-03-21 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27020 Bug ID: 27020 Summary: "command alias r run" causes an assert Product: lldb Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal

Re: [lldb-dev] Windows lldb prompt issue

2016-03-21 Thread Zachary Turner via lldb-dev
Yea Windows does have methods for doing this, it's just windows specific as you said and requires someone to actually do it. On Mon, Mar 21, 2016 at 1:50 PM Greg Clayton wrote: > You might see if there is some way to implement an equivalent of > IOHandlerEditline that works on the windows termin

Re: [lldb-dev] Windows lldb prompt issue

2016-03-21 Thread Greg Clayton via lldb-dev
Seems like there are library commands you can call: https://msdn.microsoft.com/en-us/library/windows/desktop/ms686974(v=vs.85).aspx > On Mar 21, 2016, at 1:50 PM, Greg Clayton via lldb-dev > wrote: > > You might see if there is some way to implement an equivalent of > IOHandlerEditline that

Re: [lldb-dev] Windows lldb prompt issue

2016-03-21 Thread Greg Clayton via lldb-dev
You might see if there is some way to implement an equivalent of IOHandlerEditline that works on the windows terminal? Maybe a class like IOHandlerWindowsTerminal which would be specified to native windows terminal. There has to be a way to control the cursor and do line kind of commands. I bel

Re: [lldb-dev] Windows lldb prompt issue

2016-03-21 Thread Ted Woodward via lldb-dev
I dug into this some more. Windows is not using editline, so it's using the LLDB_DISABLE_LIBEDIT code path. IOHandlerEditline::GetLine() will print the prompt, then get the next line. Type in a command, and it will continue doing this. The prompt comes out before the command finishes (in this c

Re: [lldb-dev] Windows lldb prompt issue

2016-03-21 Thread Greg Clayton via lldb-dev
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

Re: [lldb-dev] Windows lldb prompt issue

2016-03-21 Thread Zachary Turner via lldb-dev
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

[lldb-dev] Windows lldb prompt issue

2016-03-21 Thread Ted Woodward via lldb-dev
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' (