| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
debugging has a "ASTContext" that helps us to use the correct floating point semantics. Now that APFloat supports toString we now use that. If we don't have a target, we still fall back on the old display methodology, but the important formatting should always have a target available and thus use the compiler floating point code.
Modified the test programs to use floating point constants that always will display correctly. We had some numbers that were being rounded, and now that we are using clang, we no longer round them and we get more correct results.
llvm-svn: 183792
|
|
|
|
| |
llvm-svn: 183580
|
|
|
|
| |
llvm-svn: 183569
|
|
|
|
| |
llvm-svn: 183480
|
|
|
|
|
|
|
|
|
|
|
|
| |
that is patterned after its parent TestInferiorCrashing.py.
- The xfail decorator limits the xfail to tool-chains that support this compiler option.
- Included a TODO concerning the platform-specific behavior when 'next' is issued after a crash.
- Toggling -fomit-frame-pointer results in an xpass as mentioned in pr15415.
Thanks to Daniel for the review, and Samuel for the bug report and reproducer.
llvm-svn: 183434
|
|
|
|
|
|
|
|
|
| |
- one test case is due to llvm.org/pr16229
- other test case uses a Linux workaround for above by using os.fork() instead of subprocess module
Patch by Andy Kaylor!
llvm-svn: 183340
|
|
|
|
|
|
| |
- specify compiler flag -stdlib=libstdc++ only if using clang (not supported in gcc)
llvm-svn: 183333
|
|
|
|
|
|
|
| |
Adding data formatters for std::set, std::multiset and std::multimap for libc++
The underlying data structure is the same as std::map, so this change is very minimal and mostly consists of test cases
llvm-svn: 183323
|
|
|
|
| |
llvm-svn: 183316
|
|
|
|
| |
llvm-svn: 183281
|
|
|
|
|
|
|
|
|
|
| |
If you want to define a formatter for "array of Foo of any size", ordinarily you would say
-x "Foo \[[0-9]+\]"
this checkin allows you to instead say "Foo[]" (or "Foo []") and LLDB will automatically create the regular expression and add the -x flag on your behalf
llvm-svn: 183272
|
|
|
|
|
|
|
| |
- adding workaround recommended by Greg (-fno-limit-debug-info clang flag)
- filed bug llvm.org/pr16214 against Clang
llvm-svn: 183156
|
|
|
|
| |
llvm-svn: 183139
|
|
|
|
|
|
| |
- should resolve remaining buildbot issues with debian/clang builder
llvm-svn: 183044
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixing an issue where formats would not propagate from parents to children in all cases
Details follow:
an SBValue has children and those are fetched along with their values
Now, one calls SBValue::SetFormat() on the parent
Technically, the format choices should propagate onto the children (see ValueObject::GetFormat())
But if the children values are already fetched, they won't notice the format change and won't update themselves
This commit fixes that by making ValueObject::GetValueAsCString() check if any format change intervened from the previous call to the current one
A test case is also added
llvm-svn: 183030
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
command script import now does reloads - for real
If you invoke command script import foo and it detects that foo has already been imported, it will
- invoke reload(foo) to reload the module in Python
- re-invoke foo.__lldb_init_module
This second step is necessary to ensure that LLDB does not keep cached copies of any formatter, command, ... that the module is providing
Usual caveats with Python imports persist. Among these:
- if you have objects lurking around, reloading the module won't magically update them to reflect changes
- if module A imports module B, reloading A won't reload B
These are Python-specific issues independent of LLDB that would require more extensive design work
The --allow-reload (-r) option is maintained for compatibility with existing scripts, but is clearly documented as redundant - reloading is always enabled whether you use it or not
llvm-svn: 182977
|
|
|
|
|
|
|
|
| |
step-in in addition to step-inst
Patch by Brian Minard!
llvm-svn: 182961
|
|
|
|
| |
llvm-svn: 182943
|
|
|
|
| |
llvm-svn: 182888
|
|
|
|
|
|
|
|
| |
- The original test now passes on Linux with clang because a breakpoint is hit prior to evaluation of text_list, which improves text coverage.
- The new test fails because 4 steps are requested, and only two occur prior to evaluation of text_list.
--- Note that the loss of every second "next" command can be reproduced using lldb manually with this script.
llvm-svn: 182860
|
|
|
|
| |
llvm-svn: 182813
|
|
|
|
|
|
| |
Also adding multithreaded test cases.
llvm-svn: 182809
|
|
|
|
|
|
| |
Add test case to make sure we don't regress on fat files full of skinny BSD archives.
llvm-svn: 182440
|
|
|
|
| |
llvm-svn: 182429
|
|
|
|
|
|
|
|
| |
exec'ing itself into a new program. This currently is only enabled for Darwin since we exec from 64 bit to 32 bit and vice versa for 'x86_64' targets.
This can easily be adapted for linux and other platforms, but I didn't want to break any buildbots by assuming it will work.
llvm-svn: 182428
|
|
|
|
|
|
| |
- Used xfail and skip, temporarily, while resolving bugzilla #15671.
llvm-svn: 182159
|
|
|
|
|
|
|
|
|
|
| |
- Note that this is not correct, as the failure is associated with build options of libc.so, however it's failing on a Debian buildbot that uses gcc 4.6.2 (and the real goal is a complete backtrace even with -fomit-frame-pointer).
- Adds helpers to lldbtest.py to check the expectedCompiler and expectedVersion, with an eventual goal of reducing the number of test decorators.
--- Currently allows a comparison operator and a compiler version to be specified.
--- Can be extended to support ranges of compiler versions.
llvm-svn: 182155
|
|
|
|
|
|
|
|
| |
tear-down (i.e. for CI agents that clean up artifacts aggressively).
- Uses the cwd following the model of TestPublicAPIHeaders.py
llvm-svn: 182116
|
|
|
|
|
|
|
|
|
| |
- On Linux, the partial back-trace after an assert can cause the basic test to fail as discussed on lldb-dev.
- Uses SBFrame to walk up the stack to the assert site and tests expression evaluation of locals, globals and arguments.
Thanks to Daniel for review and testing on OS/X.
llvm-svn: 182115
|
|
|
|
|
|
| |
- Also removes a redundant import statement.
llvm-svn: 182111
|
|
|
|
| |
llvm-svn: 182104
|
|
|
|
|
|
|
|
|
|
| |
OS X
- resolves llvm.org/pr14806
Patch by Matthew Sorrels!
llvm-svn: 182030
|
|
|
|
|
|
|
|
|
| |
- s/skipOnLinux/skipIfLinux/ to match style of every other decorator
- linkify bugizilla/PR numbers in comments
No intended change in functionality.
llvm-svn: 181913
|
|
|
|
|
|
|
| |
- "platform process list" command works on Linux now
- "process attach -n" (attach to process by name also works on Linux now)
llvm-svn: 181905
|
|
|
|
|
|
|
|
| |
(http://lab.llvm.org:8011/builders/lldb-x86_64-linux/builds/4124)
- maybe consider checking in the 'good' version of libedit to avoid ancient system version
llvm-svn: 181903
|
|
|
|
|
|
| |
- unable to repro locally, much like many people commenting on the issue
llvm-svn: 181833
|
|
|
|
|
|
| |
buildbots.
llvm-svn: 181789
|
|
|
|
| |
llvm-svn: 181742
|
|
|
|
|
|
|
|
|
| |
are derived registers.
- Also refactors TestRegisters.py because test_convenience_registers_with_process_attach now fails with an assert.
TODO: Cross-reference the skipOnLinux decorator with a bugzilla report after root-causing this issue.
llvm-svn: 181737
|
|
|
|
|
|
|
| |
- Also improved test coverage for passing tests to include expr/x
and a sanity check for $eax as the lower half of $rax.
llvm-svn: 181727
|
|
|
|
|
|
| |
This re-submission of this patch fixes a problem where the code sometimes caused a deadlock. The Process::SetPrivateState method was locking the Process::m_private_state variable and then later calling ThreadList::DidStop, which locks the ThreadList mutex. Other methods in ThreadList which were being called from other threads lock the ThreadList mutex and then call Process::GetPrivateState which locks the Process::m_private_state mutex. To avoid deadlocks, Process::SetPrivateState now locks the ThreadList mutex before locking the Process::m_private_state mutex.
llvm-svn: 181609
|
|
|
|
|
|
| |
the automated tests and testing at the lldb command-line.
llvm-svn: 181602
|
|
|
|
|
|
| |
locals, arguments, registers and the back-trace.
llvm-svn: 181599
|
|
|
|
|
|
|
|
|
|
| |
- Eliminated the use of static for methods that read m_register_infos, so that these routines can be implemented in the base class.
- Eliminated m_register_infos in the base class because this is not used when derived classes call UpdateRegisterInfo.
- Also moved the namespace using declarations from headers to source files.
Thanks to Daniel and Samuel for their review feedback.
llvm-svn: 181538
|
|
|
|
| |
llvm-svn: 181526
|
|
|
|
|
|
|
|
| |
on the nexting always "getting it right" to stop at the locations of interest
This should make us more robust in the face of changing compiler line tables and other library modifications
llvm-svn: 181497
|
|
|
|
|
|
| |
process attach. Otherwise the target isn't valid. This fixes 2 test suite failures on darwin.
llvm-svn: 181488
|
|
|
|
| |
llvm-svn: 181482
|
|
|
|
| |
llvm-svn: 181472
|
|
|
|
|
|
| |
in the debian buildbot.
llvm-svn: 181454
|