Re: [Lldb-commits] [lldb] r219102 - Call SBDebugger::Initialize/Terminate from within Create/Destroy.

Hi Ed, Which test was the first to segfault in the suite. I've looked at the stdio page from the check-lldb target from the attached link, and it looks like it's this statement which indicates the bot failure: FAIL: LLDB (suite) :: TestFormattersSBAPI.py (FreeBSD llvm-amd64.freebsd.your.org

Re: [Lldb-commits] [lldb] r219102 - Call SBDebugger::Initialize/Terminate from within Create/Destroy.

On 7 October 2014 02:18, Matthew Gardiner m...@csr.com wrote: Hi Ed, Which test was the first to segfault in the suite. I've looked at the stdio page from the check-lldb target from the attached link, and it looks like it's this statement which indicates the bot failure: FAIL: LLDB (suite)

Re: [Lldb-commits] [lldb] r219102 - Call SBDebugger::Initialize/Terminate from within Create/Destroy.

Ok, Thanks Ed, I've just installed FreeBSD-10.0 (amd64) on VirtualBox. Have installed virtualbox-ose-additions, and gnome2. Unfortunately X (i.e. gnome) freezes on startup (i.e. won't accept kdb or mouse input). Perhaps I should just struggle on with just running in text mode, but having makes

Re: [Lldb-commits] [lldb] r219102 - Call SBDebugger::Initialize/Terminate from within Create/Destroy.

On 7 October 2014 09:34, Matthew Gardiner m...@csr.com wrote: Ok, Thanks Ed, I've just installed FreeBSD-10.0 (amd64) on VirtualBox. Have installed virtualbox-ose-additions, and gnome2. Unfortunately X (i.e. gnome) freezes on startup (i.e. won't accept kdb or mouse input). Perhaps I should

Re: [Lldb-commits] [PATCH] spurious output to command line when launching a process on linux

Testing this over here now. http://reviews.llvm.org/D5632 ___ lldb-commits mailing list lldb-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] r219245 - The type category enable * was implemented assuming a previous disable * had happened. While that will most likely be true in practice, the consequences of this not bei

Author: enrico Date: Tue Oct 7 17:15:27 2014 New Revision: 219245 URL: http://llvm.org/viewvc/llvm-project?rev=219245view=rev Log: The type category enable * was implemented assuming a previous disable * had happened. While that will most likely be true in practice, the consequences of this

Re: [Lldb-commits] [PATCH] Add target.jit-args settings

Heads up. This patch seems to be the cause of http://llvm.org/bugs/show_bug.cgi?id=21190 http://llvm.org/bugs/show_bug.cgi?id=21190 Essentially, the command parser gets confused with commands like: type summary add Rectangle --summary-string Category1 -w Category1 and the value for the -w

[Lldb-commits] [lldb] r219247 - When we detect a stack unwind loop, before we abort

Author: jmolenda Date: Tue Oct 7 17:55:13 2014 New Revision: 219247 URL: http://llvm.org/viewvc/llvm-project?rev=219247view=rev Log: When we detect a stack unwind loop, before we abort the backtrace, try falling back to the architecture default unwind plan and see if we can backtrace a little

[Lldb-commits] [lldb] r219251 - Update TestInlinedBreakpoints to reflect the fact that

Author: jmolenda Date: Tue Oct 7 18:37:28 2014 New Revision: 219251 URL: http://llvm.org/viewvc/llvm-project?rev=219251view=rev Log: Update TestInlinedBreakpoints to reflect the fact that the default search method is always as of r218405. For the purposes of this test, set it back to headers to

[Lldb-commits] [lldb] r219269 - Minor comment change to test out svn access

Author: sbest Date: Tue Oct 7 20:50:37 2014 New Revision: 219269 URL: http://llvm.org/viewvc/llvm-project?rev=219269view=rev Log: Minor comment change to test out svn access Modified: lldb/trunk/source/Target/Process.cpp Modified: lldb/trunk/source/Target/Process.cpp URL: