The disappearing (lldb) prompt and a few similar bugs are theoretically
present on OSX. I can easily reproduce them with inserting a small
delay to provoke a context switch, delaying the call to push the io handler.
Shawn.
On 8/4/2014 10:01 PM, Matthew Gardiner wrote:
Thanks for this
Author: emaste
Date: Tue Aug 5 12:50:04 2014
New Revision: 214900
URL: http://llvm.org/viewvc/llvm-project?rev=214900view=rev
Log:
On FreeBSD skip test that produces bogus output
The test produces lines that start with word: which confuses the
buildbot log parser. Disable the test until
Author: emaste
Date: Tue Aug 5 15:33:17 2014
New Revision: 214922
URL: http://llvm.org/viewvc/llvm-project?rev=214922view=rev
Log:
Force trace on system() failure on FreeBSD while tracking down buildbot issues
Modified:
lldb/trunk/test/lldbtest.py
Modified: lldb/trunk/test/lldbtest.py
Author: jingham
Date: Tue Aug 5 19:24:38 2014
New Revision: 214941
URL: http://llvm.org/viewvc/llvm-project?rev=214941view=rev
Log:
Probably should initialize that new ivar while I'm at it...
Modified:
lldb/trunk/source/Interpreter/CommandObject.cpp
Modified:
Author: jingham
Date: Tue Aug 5 20:49:59 2014
New Revision: 214946
URL: http://llvm.org/viewvc/llvm-project?rev=214946view=rev
Log:
When stepping, handle the case where the step leaves us with
the same parent frame, but different current frame - e.g. when
you step past a tail call exit from a
I looked how it is done in gdb, and found that this piece of code must be
rewritten.
http://reviews.llvm.org/D4803
Files:
source/Plugins/Process/Linux/NativeProcessLinux.cpp
Index: source/Plugins/Process/Linux/NativeProcessLinux.cpp
