| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
source/API; other minor fixes.
Other fixes should reduce number of readability-redundant-smartptr-get and readability-implicit-bool-cast.
llvm-svn: 251733
|
|
|
|
| |
llvm-svn: 251732
|
|
|
|
|
|
| |
source/Expression and tools/lldb-mi; other minor fixes.
llvm-svn: 251730
|
|
|
|
|
|
| |
in breakpoint conditions.
llvm-svn: 251727
|
|
|
|
| |
llvm-svn: 251722
|
|
|
|
| |
llvm-svn: 251721
|
|
|
|
| |
llvm-svn: 251720
|
|
|
|
|
|
| |
minor fixes.
llvm-svn: 251716
|
|
|
|
| |
llvm-svn: 251704
|
|
|
|
|
|
|
| |
I don't think anything has changed recently - the test was always flaky, but
only very rarely. Still, it is causing noise in the buildbots.
llvm-svn: 251699
|
|
|
|
| |
llvm-svn: 251684
|
|
|
|
|
|
|
|
|
| |
These are two simple tests that make sure single line and
multiline content are processed and received by Editline.cpp.
Fancier tests to come...
llvm-svn: 251681
|
|
|
|
|
|
|
|
|
|
| |
was turning out to be None even though it was being validly set by dotest.py
It turns out that lldbtest_config was being imported locally to "lldbsuite.test" instead of globally, so when the test cases got individually brought by a global import via __import__ by unittest2, they did not see the lldbtest_config import, and ended up importing a new separate copy of it, with lldbExec unset
This is a simple hackaround that brings lldbtest_config to global visibility and makes sure the configuration data is correctly shared
llvm-svn: 251678
|
|
|
|
|
|
| |
source/Plugins/Process/Utility headers; other minor fixes.
llvm-svn: 251676
|
|
|
|
|
|
| |
minor fixes.
llvm-svn: 251673
|
|
|
|
|
|
| |
don't really want
llvm-svn: 251670
|
|
|
|
|
|
| |
type, how many sizeof(type) bytes to speak before starting to read memory
llvm-svn: 251668
|
|
|
|
| |
llvm-svn: 251663
|
|
|
|
|
|
|
|
|
| |
allow removing formatters from language categories
This is slightly harder to test because formatters cannot be added to language categories, so deletions are irreversible (in a debugger run)
I plan to add a test case soon, but I need to think about the right approach to obtain one
llvm-svn: 251660
|
|
|
|
|
|
| |
TestCompletions.py).
llvm-svn: 251657
|
|
|
|
|
|
| |
include/lldb/Target; other minor fixes.
llvm-svn: 251648
|
|
|
|
|
|
| |
include/lldb/Target; other minor fixes.
llvm-svn: 251647
|
|
|
|
|
|
| |
TypeSummaryImpl
llvm-svn: 251642
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
I observed that eclipse was passing --thread-group for many other commands
then we are currently handling. Looking at the MI documentation, the
following link states that each MI command accept the --thread and
--frame option. Looking at the GDB implementation, it seems that apart
from these 2, --thread-group is also handled the same way.
https://sourceware.org/gdb/onlinedocs/gdb/Context-management.html#Context-management
So instead of handling those arguments in every comamnds, I have moved
them into the base class and removed them from elsewhere. Now any command
can use these arguments. The patch seems big but most of the changes are
mechanical.
Reviewers: ki.stfu
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D14177
llvm-svn: 251636
|
|
|
|
|
|
| |
forgot to rename in one spot.
llvm-svn: 251628
|
|
|
|
|
|
|
|
|
|
|
| |
The test was verifying that the pid of the child is not equal to its process
group by searching for text substrings. This failed in the rare cases when the
pid actually *was* a substring of the process group (even though they were not
equal).
Change the test to use SB API and do proper numeric comparisons.
llvm-svn: 251626
|
|
|
|
|
|
| |
http://reviews.llvm.org/D14169
llvm-svn: 251616
|
|
|
|
|
|
| |
there must be (at least) one more race hidden there...
llvm-svn: 251590
|
|
|
|
|
|
|
|
|
|
| |
Reviewers: sas, ovyalov
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D14166
llvm-svn: 251589
|
|
|
|
|
|
| |
Host; other minor fixes.
llvm-svn: 251587
|
|
|
|
|
|
|
| |
(whatever that is) and wanted to clean up some duplicated
entries in the project files.
llvm-svn: 251586
|
|
|
|
| |
llvm-svn: 251585
|
|
|
|
|
|
| |
be used. Guard against that.
llvm-svn: 251584
|
|
|
|
|
|
|
| |
has tested that sc.function is null, it would try to deref sc.function.
It should be calling sc.symbol here.
llvm-svn: 251583
|
|
|
|
| |
llvm-svn: 251581
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and decided to not commit the change, but accidentally committed
it anyway.
This was based on a static analysis complaint; it thought there
was a code path where AdbClient::PushFile would call AdbClient::ReadSyncHeader
and AdbClient::ReadSyncHeader wouldn't set data_len. But in that
case, the Error object returned will be Fail and we won't use
the data_len or response_id contents.
llvm-svn: 251580
|
|
|
|
|
|
|
|
| |
use the CPU type and subtype to fill out an architecture. We do this by letting the vendor be an unspecified unknown, or any. We also grab the target architecture, get the KDP host arch, and then merge the two before putting it back into the target.
Also change MH_PRELOAD to be use "unspecified unknown" (any) for the OS and vendor since these mach files can really be anything.
llvm-svn: 251579
|
|
|
|
| |
llvm-svn: 251578
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
than a
StackFrame * (StackFrame is an ExecutionContextScope.) That allows you to call an
expression on a particular Thread, but not using the context of any particular frame.
That in turn is useful for injecting utility functions that don't actually depend on
locals/self/etc of the current frame.
I also had to include StackFrame.h in a couple of places so the compiler knew
how to downcast StackFrame to ExecutionContextScope.
<rdar://problem/22852953>
llvm-svn: 251564
|
|
|
|
| |
llvm-svn: 251563
|
|
|
|
|
|
| |
include/lldb/Core; other minor fixes.
llvm-svn: 251561
|
|
|
|
|
|
| |
WindowServer access
llvm-svn: 251559
|
|
|
|
|
|
| |
include/lldb/Core; other minor fixes.
llvm-svn: 251556
|
|
|
|
|
|
| |
<rdar://problem/21991784>
llvm-svn: 251555
|
|
|
|
| |
llvm-svn: 251550
|
|
|
|
|
|
| |
on some Windows machines.
llvm-svn: 251549
|
|
|
|
|
|
| |
http://reviews.llvm.org/D14126
llvm-svn: 251547
|
|
|
|
|
|
|
|
| |
It's complaining that it doesn't under the "import" command, so
I guess I need this hashbang at the beginning so that it knows
it's a Python script.
llvm-svn: 251544
|
|
|
|
| |
llvm-svn: 251542
|
|
|
|
|
|
| |
dump debugging.
llvm-svn: 251540
|