| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
Add a callback that will allow an expression to be cancelled between the
expression evaluation stages (for the ClangUserExpressions.)
<rdar://problem/16790467>, <rdar://problem/16573440>
llvm-svn: 207944
|
|
|
|
|
|
| |
SIZE_MAX here.
llvm-svn: 207855
|
|
|
|
|
|
|
|
|
|
|
|
| |
- CTRL+C wasn't clearing the command in lldb
- CTRL+C doesn't work in python macros in lldb
- Ctrl+C no longer interrupts the running process that you attach to
<rdar://problem/15949205>
<rdar://problem/16778652>
<rdar://problem/16774411>
llvm-svn: 207816
|
|
|
|
|
|
|
|
|
|
| |
when we quit.
Currently if you run _any_ python, python has the "lldb.debugger" global variable and it has a strong reference to a lldb_private::Debugger since it is a lldb::SBDebugger object with a shared pointer.
This makes sure that your LLDB command interpreter history is saved each time you quit command line LLDB.
llvm-svn: 207164
|
|
|
|
|
|
|
|
|
|
| |
mappings would get messed up.
I fixed this by only doing el_set(e, EL_BIND, ...) calls before sourcing the .editrc files.
<rdar://problem/16614095>
llvm-svn: 207005
|
|
|
|
|
|
|
|
|
| |
Set the correct FormatManager revision before starting to figure out the new formatters
This can avoid entering some corner cases where as part of figuring out formatters we try to figure out dynamic types, and in turn that causes us to go back in trying to fetch new formatters - it is not only a futile exercise, it's also prone to endless recursion
This would only cause a behavior change if getting this chain started would eventually cause something to run and alter the formatters, a very unlikely if at all possible sequence of events
llvm-svn: 205928
|
|
|
|
|
|
|
|
|
|
| |
TIDs are conventionally shown as decimal values on FreeBSD and Linux.
Thus, use the ${thread.id%tid} format string to display the thread ID,
instead of a fixed hex format.
llvm.org/pr19380
llvm-svn: 205912
|
|
|
|
|
|
|
| |
error: declaration of constexpr static data member 'spec' requires an
initializer
llvm-svn: 205776
|
|
|
|
| |
llvm-svn: 205770
|
|
|
|
| |
llvm-svn: 205769
|
|
|
|
|
|
|
|
| |
that isn't EINTR.
<rdar://problem/16535437>
llvm-svn: 205740
|
|
|
|
|
|
| |
calling fgets().
llvm-svn: 205638
|
|
|
|
|
|
|
| |
This is a purely mechanical change explicitly casting any parameters for printf
style conversion. This cleans up the warnings emitted by gcc 4.8 on Linux.
llvm-svn: 205607
|
|
|
|
|
|
|
|
|
|
| |
headers
on Mac OS X (in particular mach/machine.h).
<rdar://problem/16494607>
llvm-svn: 205480
|
|
|
|
|
|
|
|
| |
This is a mechanical change addressing the various sign comparison warnings that
are identified by both clang and gcc. This helps cleanup some of the warning
spew that occurs during builds.
llvm-svn: 205390
|
|
|
|
|
|
|
|
| |
For some reason, the libc++ vector<bool> data formatter was essentially a costly no-up, doing everything required of it, except actually generating the child values!
This restores its functionality
llvm-svn: 205259
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These changes were written by Greg Clayton, Jim Ingham, Jason Molenda.
It builds cleanly against TOT llvm with xcodebuild. I updated the
cmake files by visual inspection but did not try a build. I haven't
built these sources on any non-Mac platforms - I don't think this
patch adds any code that requires darwin, but please let me know if
I missed something.
In debugserver, MachProcess.cpp and MachTask.cpp were renamed to
MachProcess.mm and MachTask.mm as they picked up some new Objective-C
code needed to launch processes when running on iOS.
llvm-svn: 205113
|
|
|
|
|
|
|
| |
For small structs, the frame format now prints them as one-liners
This follows the same definition that frame variable does for deciding what a "small struct" is, and as such should be fairly consistent with the variable display in general
llvm-svn: 204762
|
|
|
|
|
|
|
| |
Add a GetFoundationVersion() to AppleObjCRuntime
This API is used to return and cache the major version of Foundation.framework, which is potentially a useful piece of data to key off of to enable or disable certain ObjC related behaviors (especially in data formatters)
llvm-svn: 204756
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
source info:
(lldb) b puts
(lldb) expr -g -i0 -- (int)puts("hello")
First we will stop at the entry point of the expression before it runs, then we can step over a few times and hit the breakpoint in "puts", then we can continue and finishing stepping and fininsh the expression.
Main features:
- New ObjectFileJIT class that can be easily created for JIT functions
- debug info can now be enabled when parsing expressions
- source for any function that is run throught the JIT is now saved in LLDB process specific temp directory and cleaned up on exit
- "expr -g --" allows you to single step through your expression function with source code
<rdar://problem/16382881>
llvm-svn: 204682
|
|
|
|
| |
llvm-svn: 204632
|
|
|
|
|
|
| |
safe and also fixed a missed member initialization on the copy contractor and also makes the assignment operator safer.
llvm-svn: 204622
|
|
|
|
|
|
| |
No functionnal change.
llvm-svn: 204545
|
|
|
|
|
|
| |
to keep the code more portable as we add new core types to ArchSpec.
llvm-svn: 204400
|
|
|
|
| |
llvm-svn: 204359
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanical cleanup of unused functions. In the case where the
functions are referenced (in comment form), I've simply commented out the
functions. A second pass to clean that up is warranted.
The functions which are otherwise unused have been removed. Some of these were
introduced in the initial commit and not in use prior to that point!
NFC
llvm-svn: 204310
|
|
|
|
|
|
|
|
|
|
| |
TestPromptFormats appears as though it may be a useful unit test.
Unfortunately, there is no invocation mechanism in place right now. It is
unclear how to add a unit test for this scenario to the existing tests. It
would be ideal to remove this entirely, but I am hopeful that this can/will be
pulled out into a test still since it uses a user accessible interface.
llvm-svn: 204309
|
|
|
|
|
|
| |
process, its threads and see all frames under each thread.
llvm-svn: 204251
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that it is useful not only
for customizing "step-in" behavior (e.g. step-in doesn't step into code with no debug info), but also
the behavior of step-in/step-out and step-over when they step out of the frame they started in.
I also added as a proof of concept of this reworking a mode for stepping where stepping out of a frame
into a frame with no debug information will continue stepping out till it arrives at a frame that does
have debug information. This is useful when you are debugging callback based code where the callbacks
are separated from the code that initiated them by some library glue you don't care about, among other
things.
llvm-svn: 203747
|
|
|
|
|
|
|
| |
This allows to use some code for mingw which was previously only
used for MSVC.
llvm-svn: 203651
|
|
|
|
|
|
|
|
|
|
| |
evaluate, make sure
we actually got something before proceeding.
<rdar://problem/16282875>
llvm-svn: 203591
|
|
|
|
| |
llvm-svn: 203533
|
|
|
|
| |
llvm-svn: 203505
|
|
|
|
|
|
|
|
|
|
| |
Thread) calls
or the lower levels of the Process won't be able to restart.
<rdar://problem/16244835>
llvm-svn: 203233
|
|
|
|
| |
llvm-svn: 203185
|
|
|
|
|
|
|
|
| |
the header files were in "include/lldb/Target".
Also enabled the ELF Core file support in all builds since the header files have been properly separated from ProcessMonitor.
llvm-svn: 203035
|
|
|
|
|
|
| |
written with Keno Fischer.
llvm-svn: 202956
|
|
|
|
|
|
|
|
|
| |
don't pickup bogus locally cached files.
<rdar://problem/16217254>
<rdar://problem/16078651>
llvm-svn: 202890
|
|
|
|
|
|
| |
problems with the testsuite and SBDebugger::CreateTarget().
llvm-svn: 202776
|
|
|
|
|
|
|
|
| |
style statements that were assuming size_t were 64 bit were changed, and they were also changed to display them as unsigned values as "size_t" isn't signed.
If you print anything with 'size_t', please cast it to "uint64_t" in the printf and use PRIu64 or PRIx64.
llvm-svn: 202738
|
|
|
|
| |
llvm-svn: 202723
|
|
|
|
|
|
|
|
|
|
|
| |
read during materialization. First of all, report
if we can't read the data for some reason. Second,
consult the ValueObject's error and report that if
there's some problem.
<rdar://problem/16074201>
llvm-svn: 202552
|
|
|
|
| |
llvm-svn: 202535
|
|
|
|
|
|
|
|
| |
I carefully reviewed exactly how the IOHandlers interact and found places where we weren't properly controlling things. There should be no overlapping prompts and all output should now come out in a controlled fashion.
<rdar://problem/16111293>
llvm-svn: 202525
|
|
|
|
| |
llvm-svn: 202440
|
|
|
|
|
|
| |
process again.
llvm-svn: 202086
|
|
|
|
| |
llvm-svn: 201665
|
|
|
|
|
|
|
| |
Revert the spirit of r199857 - a convincing case can be made that overriding a summary's format markers behind its back is not the right thing to do
This commit reverts the behavior of the code to the previous model, and changes the test case to validate the opposite of what it was validating before
llvm-svn: 201455
|
|
|
|
|
|
|
|
|
| |
operating system plugins, and other async python usage.
<rdar://problem/16054348>
<rdar://problem/16040833>
llvm-svn: 201372
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ObjectFile::SetLoadAddress (Target &target,
lldb::addr_t value,
bool value_is_offset);
Now "value" is a slide if "value_is_offset" is true, and "value" is an image base address otherwise. All previous usage of this API was using slides.
Updated the ObjectFileELF and ObjectFileMachO SetLoadAddress methods to do the right thing.
Also updated the ObjectFileMachO::SetLoadAddress() function to not load __LINKEDIT when it isn't needed and to only load sections that belong to the executable object file.
llvm-svn: 201003
|