| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 192462
|
| |
|
|
|
|
|
|
|
|
| |
MIPS's .dyanamic section is read-only. Instead of using DT_DEBUG for
the pointer to dyld information it uses a separate tag DT_MIPS_RLD_MAP
which points to storage in the read-write .rld_map section, which in
turn points to the dyld information.
Review: http://llvm-reviews.chandlerc.com/D1890
llvm-svn: 192408
|
| |
|
|
| |
llvm-svn: 192388
|
| |
|
|
|
|
|
| |
Committing early to ease tracking other ongoing POSIX changes.
Review: http://llvm-reviews.chandlerc.com/D1886
llvm-svn: 192387
|
| |
|
|
|
|
| |
Fixed an issue where environment variables that contained special characters '$' and '#' would hose up the GDB server packet. We now use the QEnvironmentHexEncoded packet that has existed for a long time when we need to. Also added code that will stop sending the QEnvironmentHexEncoded and QEnvironment packets if they aren't supported.
llvm-svn: 192373
|
| |
|
|
|
|
|
|
| |
On at least FreeBSD and NetBSD there is an extra field in the dyld link
map struct. I've left an assert for other OSes (i.e., Linux/mips) until
it's determined if they do the same.
llvm-svn: 192358
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Based on the POSIX x86_64 register context. This is sufficient for opening
a mips64 (big endian) core file. Subsequent changes will connect the
disassembler, dynamic loader support, ABI, etc.
Review: http://llvm-reviews.chandlerc.com/D1873
(Missed "svn add" on this file in r192335)
llvm-svn: 192336
|
| |
|
|
|
|
|
|
|
| |
Based on the POSIX x86_64 register context. This is sufficient for opening
a mips64 (big endian) core file. Subsequent changes will connect the
disassembler, dynamic loader support, ABI, etc.
Review: http://llvm-reviews.chandlerc.com/D1873
llvm-svn: 192335
|
| |
|
|
|
|
|
|
|
| |
made sure we don't keep around no-longer-valid
ASTTransformers.
<rdar://problem/15182379>
llvm-svn: 192333
|
| |
|
|
|
|
| |
RegisterContextPOSIX_x86
llvm-svn: 192332
|
| |
|
|
|
|
|
|
|
| |
importer to avoid duplicate imports of anonymous
structs.
<rdar://problem/14421722>
llvm-svn: 192327
|
| |
|
|
|
|
|
|
|
|
|
|
| |
ObjectFile::CopyData is used to copy a block of target memory to the
caller's buffer (e.g. for "memory read"). This should be a straight
memcpy, and not byte-swapped if the target and host have different
endianness.
Add a new DataExtractor::CopyData() method that performs this straight
copy and use it in ObjectFile::CopyData().
llvm-svn: 192323
|
| |
|
|
| |
llvm-svn: 192322
|
| |
|
|
| |
llvm-svn: 192319
|
| |
|
|
|
|
| |
case of exec).
llvm-svn: 192318
|
| |
|
|
| |
llvm-svn: 192307
|
| |
|
|
|
|
| |
Remove 32-bit POSIX register hack in ConvertBetweenRegisterKinds.
llvm-svn: 192306
|
| |
|
|
|
|
|
|
|
| |
already in the stopped state
- By default, the above function will wait for at least one event
- Set wait_always=false to make the function return immediately if the process is already stopped
llvm-svn: 192301
|
| |
|
|
| |
llvm-svn: 192296
|
| |
|
|
|
|
|
| |
with no source-level debug information correctly.
<rdar://problem/15182936>
llvm-svn: 192268
|
| |
|
|
|
|
|
|
|
| |
respect their Clang types if the variables' values
were represented by DWARF constu values.
<rdar://problem/14636499>
llvm-svn: 192267
|
| |
|
|
|
|
|
|
| |
wrong information to ValueObjectConstResult.
<rdar://problem/15101795>
llvm-svn: 192264
|
| |
|
|
|
|
|
|
|
|
|
| |
Use 32-bit register enums without gaps on 64-bit hosts.
Don't show 64-bit registers when debugging 32-bit targets.
Add psuedo gpr registers (ax, ah, al, etc.)
Add mmx registers.
Fix TestRegisters.py to not read ymm15 register on 32-bit targets.
Fill out and move gcc/dwarf/gdb register enums to RegisterContext_x86.h
llvm-svn: 192263
|
| |
|
|
|
|
|
|
| |
Constant ValueObjects should clear their description as well as their summary. Rationale being that both can depend on deeper-than-constified data
so both are subject to changes in "unpredictable" ways
To see this consider repeatedly po'ing a persistent variable of a type whose -description result changes at each invocation
llvm-svn: 192259
|
| |
|
|
|
|
| |
Making GetNumberOfDirectBaseClasses() work for ObjC pointers, and for classes for which we don't have full debug info
llvm-svn: 192255
|
| |
|
|
|
|
|
| |
Implement SBTarget::CreateValueFromAddress() with a behavior equivalent to SBValue::CreateValueFromAddress()
(but without the need to grab an SBValue first just as a starting point to make up another SBValue out of whole cloth)
llvm-svn: 192239
|
| |
|
|
|
|
|
|
| |
Add a format for FourCharCode
This is now safe to do thanks to the "formats in categories" feature
llvm-svn: 192233
|
| |
|
|
|
|
|
| |
Formats (as in "type format") are now included in categories
The only bit missing is caching formats along with synthetic children and summaries, which might be now desirable
llvm-svn: 192217
|
| |
|
|
|
|
| |
<rdar://problem/15099306>
llvm-svn: 192161
|
| |
|
|
| |
llvm-svn: 192155
|
| |
|
|
|
|
| |
checkin fixes that
llvm-svn: 192116
|
| |
|
|
|
|
| |
http://buildd-clang.debian.net/scan-build/
llvm-svn: 192060
|
| |
|
|
|
|
| |
versions of GCC
llvm-svn: 192013
|
| |
|
|
|
|
|
| |
Several CF* data formatters were in the AppKit category
This puts them back where they belong, i.e. in category CoreFoundation
llvm-svn: 192008
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This radar extends the notion of one-liner summaries to automagically apply in a few interesting cases
More specifically, this checkin changes the printout of ValueObjects to print on one-line (as if type summary add -c had been applied) iff:
this ValueObject does not have a summary
its children have no synthetic children
its children are not a non-empty base class without a summary
its children do not have a summary that asks for children to show up
the aggregate length of all the names of all the children is <= 50 characters
you did not ask to see the types during a printout
your pointer depth is 0
This is meant to simplify the way LLDB shows data on screen for small structs and similarly compact data types (e.g. std::pair<int,int> anyone?)
Feedback is especially welcome on how the feature feels and corner cases where we should apply this printout and don't (or viceversa, we are applying it when we shouldn't be)
llvm-svn: 191996
|
| |
|
|
|
|
|
|
|
|
| |
that all clients use them explicitly. This will hopefully
prevent any future confusion where things get cast to types
we don't expect.
<rdar://problem/15146458>
llvm-svn: 191984
|
| |
|
|
| |
llvm-svn: 191974
|
| |
|
|
| |
llvm-svn: 191972
|
| |
|
|
| |
llvm-svn: 191960
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to be explicit, to prevent horrid things like
std::string a = ConstString("foo")
from taking the path ConstString -> bool -> char
-> std::string.
This fixes, among other things, ClangFunction.
<rdar://problem/15137989>
llvm-svn: 191934
|
| |
|
|
| |
llvm-svn: 191919
|
| |
|
|
|
|
|
| |
in the unwinder - they're important to flag when debugging an
unwind problem.
llvm-svn: 191882
|
| |
|
|
|
|
| |
Fix an issue with the new ValueObjectPrinter where in some cases spurious \n would be printed
llvm-svn: 191869
|
| |
|
|
|
|
| |
clear what is happening in this case.
llvm-svn: 191860
|
| |
|
|
| |
llvm-svn: 191837
|
| |
|
|
|
|
|
| |
To support cross-endian and big-endian debugging avoid copying target
memory directly into host variables.
llvm-svn: 191826
|
| |
|
|
| |
llvm-svn: 191806
|
| |
|
|
|
|
| |
- delegating c'tors not supported
llvm-svn: 191709
|
| |
|
|
| |
llvm-svn: 191703
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DumpValueObject() 2.0
This checkin restores pre-Xcode5 functionality to the "po" (expr -O) command:
- expr now has a new --description-verbosity (-v) argument, which takes either compact or full as a value (-v is the same as -vfull)
When the full mode is on, "po" will show the extended output with type name, persistent variable name and value, as in
(lldb) expr -O -v -- foo
(id) $0 = 0x000000010010baf0 {
1 = 2;
2 = 3;
}
When -v is omitted, or -vcompact is passed, the Xcode5-style output will be shown, as in
(lldb) expr -O -- foo
{
1 = 2;
2 = 3;
}
- for a non-ObjectiveC object, LLDB will still try to retrieve a summary and/or value to display
(lldb) po 5
5
-v also works in this mode
(lldb) expr -O -vfull -- 5
(int) $4 = 5
On top of that, this is a major refactoring of the ValueObject printing code. The functionality is now factored into a ValueObjectPrinter class for easier maintenance in the future
DumpValueObject() was turned into an instance method ValueObject::Dump() which simply calls through to the printer code, Dump_Impl has been removed
Test case to follow
llvm-svn: 191694
|