summaryrefslogtreecommitdiffstats
path: root/lldb/test/expression_command
Commit message (Collapse)AuthorAgeFilesLines
* If a hand-called function is interrupted by hitting a breakpoint, then Jim Ingham2014-07-082-0/+73
| | | | | | | when you continue to finish off the function call, the expression result will be included as part of the thread stop info. llvm-svn: 212506
* Marked TestFormatters.py XFAIL on Linux per pr20230.Todd Fiala2014-07-071-0/+1
| | | | | | See http://www.llvm.org/bugs/show_bug.cgi?id=20230 for details. llvm-svn: 212486
* Fix interval recalculation in the event that usleep is interruptedEd Maste2014-04-291-1/+1
| | | | llvm-svn: 207566
* Add decorator for FreeBSD buildbot failureEd Maste2014-04-291-0/+1
| | | | | | llvm.org/pr19605 llvm-svn: 207557
* Remove decorator for now-passing testEd Maste2014-04-211-1/+0
| | | | | | | | | | The underlying issue was actually a Clang bug, now fixed. The test now reports XPASS for me locally and on the buildbot. llvm.org/pr17183 (LLDB) llvm.org/pr18950 (Clang) llvm-svn: 206761
* Add the ability from the SB API's to set the "one thread" timeoutJim Ingham2014-03-281-0/+10
| | | | | | | | for expression evaluations that try one and then all threads. <rdar://problem/15598528> llvm-svn: 205060
* Fixed up intermittently failing tests to skip on Linux.Todd Fiala2014-03-251-0/+1
| | | | | | | | | | | Also added 'import sys' on some tests that are using non-standard unittest2.skipUnless blocks with code that is intended to do things that we have more specializes @* attributes for. These skip conditions were failing to execute due to missing import, causing darwin-only tests to run on Linux regardless. Will file a bug for that separately. llvm-svn: 204747
* Add annotation for test failure due to clang 3.4Ed Maste2014-03-241-0/+1
| | | | | | | | | | FreeBSD recently updated to Clang 3.4 and the TestFormatters test case started failing as it omits the C1 complete object constructor when not needed. llvm.org/pr19011 llvm-svn: 204652
* expectedFailureDarwin for this test case.Jim Ingham2014-03-201-0/+2
| | | | llvm-svn: 204287
* Expected failure printing std::string::c_str() due to flubbing the typedef ↵Jim Ingham2014-03-191-6/+4
| | | | | | lookup. llvm-svn: 204206
* Update test class name and comment to match testEd Maste2014-03-031-2/+2
| | | | llvm-svn: 202718
* Restore signal delivery to the inferior on FreeBSDEd Maste2014-02-281-1/+0
| | | | | | | This was broken in the threaded inferior implementation for FreeBSD (r196787) and caused FreeBSD to resume always with no signal. llvm-svn: 202513
* Enable TestCallThatRestarts test on Linux.Todd Fiala2014-02-281-1/+0
| | | | | | | | | | This is related to: http://llvm.org/bugs/show_bug.cgi?id=15278 I ran this 20 times in a row without failure at svn r202440 on Ubuntu 12.04 LTS x86_64 using July 2013 libedit and gcc 4.8.2. llvm-svn: 202448
* Remove decorator for llvm.org/pr17233Ed Maste2014-02-111-1/+0
| | | | | | | This test was skipped as it used to segfault on FreeBSD. It seems the original issue has since been fixed, so have the test run again. llvm-svn: 201169
* Correctly set the working directory when launching processes for both local ↵Greg Clayton2013-12-135-5/+5
| | | | | | and remote targets. llvm-svn: 197266
* Make this test an expected fail on darwin until we can fix this bug.Greg Clayton2013-12-111-1/+1
| | | | llvm-svn: 197087
* Massive test suite cleanup to stop everyone from manually having to compute ↵Greg Clayton2013-12-1015-15/+15
| | | | | | | | | | "mydir" inside each test case. This has led to many test suite failures because of copy and paste where new test cases were based off of other test cases and the "mydir" variable wasn't updated. Now you can call your superclasses "compute_mydir()" function with "__file__" as the sole argument and the relative path will be computed for you. llvm-svn: 196985
* Annotate test that fails on the FreeBSD buildbotEd Maste2013-11-211-0/+1
| | | | | | llvm.org/pr17807 llvm-svn: 195361
* This patch does a couple of things. Jim Ingham2013-11-072-1/+27
| | | | | | | | | | | | | | | | | | | | | | It completes the job of using EvaluateExpressionOptions consistently throughout the inferior function calling mechanism in lldb begun in Greg's patch r194009. It removes a handful of alternate calls into the ClangUserExpression/ClangFunction/ThreadPlanCallFunction which were there for convenience. Using the EvaluateExpressionOptions removes the need for them. Using that it gets the --debug option from Greg's patch to work cleanly. It also adds another EvaluateExpressionOption to not trap exceptions when running expressions. You shouldn't use this option unless you KNOW your expression can't throw beyond itself. This is: <rdar://problem/15374885> At present this is only available through the SB API's or python. It fixes a bug where function calls would unset the ObjC & C++ exception breakpoints without checking whether they were set by somebody else already. llvm-svn: 194182
* <rdar://problem/12042982>Enrico Granata2013-10-041-2/+2
| | | | | | | | | | | | | | | | | | | 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
* This test uses ObjC so it should not run on anything != DarwinEnrico Granata2013-09-301-0/+1
| | | | llvm-svn: 191698
* Test case for the previous checkinEnrico Granata2013-09-303-0/+89
| | | | llvm-svn: 191697
* Mark 32/64-bit tests as expected fail after root causing and referencing ↵Matt Kopec2013-09-261-1/+0
| | | | | | | | bugzilla. Fix TestFrames.py error to check against a None pc value. llvm-svn: 191470
* Add an xfail test as 'expr myfloat' can add digits consistentAshok Thirumurthi2013-09-201-1/+12
| | | | | | with the closest available 32-bit floating point representation. llvm-svn: 191101
* Skip tests that segfault or are inconsistent on FreeBSDEd Maste2013-09-131-0/+1
| | | | | | | | | | | | | I now see no unexpected failures on FreeBSD on a local run of the test suite. llvm.org/pr17214 llvm.org/pr17225 llvm.org/pr17231 llvm.org/pr17232 llvm.org/pr17233 llvm-svn: 190709
* test: Update FreeBSD failure decoratorsEd Maste2013-09-131-0/+1
| | | | | | | | | | | | | | | llvm.org/pr15261 missing size for static arrays llvm.org/pr15278 expressions generating signals llvm.org/pr15824 thread states aren't properly maintained llvm.org/pr16696 threaded inferior debugging not yet on FreeBSD llvm.org/pr17214 inline stepping fails on FreeBSD llvm.org/pr17225 Clang assertion failure llvm.org/pr17226 frame info lost after failed expression evaluation llvm.org/pr17228 test timeout The first three are existing Linux issues that also affect FreeBSD. llvm-svn: 190698
* test: Add @expectedFailureFreeBSD decoratorsEd Maste2013-09-101-0/+1
| | | | | | | http://llvm.org/pr17183 expression w/ varargs printf() fails http://llvm.org/pr15302 'anonymous namespace' prefix missing llvm-svn: 190415
* Re-enable some locally passing tests on Linux and see how they behave on the ↵Matt Kopec2013-09-061-1/+0
| | | | | | buildbots. llvm-svn: 190214
* Fix minor bugs in TestExprs and TestAliases to fix buildbot breakageDaniel Malea2013-09-051-3/+3
| | | | | | | - 'run' alias no longer includes the '--' for positional arguments... does not seem like a real bug. - 2.234f is not a great number for the float tests (due to precision/printing issues) so use 0.5f instead llvm-svn: 190100
* Expression evaluation works on FreeBSD after switch to MCJITEd Maste2013-08-304-4/+0
| | | | | | http://www.llvm.org/pr16697 llvm-svn: 189668
* Mark additional icc test failures as expected fail.Matt Kopec2013-08-021-0/+1
| | | | llvm-svn: 187660
* tests: Mark expected FreeBSD failures due to pr16697Ed Maste2013-07-302-0/+2
| | | | llvm-svn: 187415
* tests: Mark expected FreeBSD failures due to pr16697Ed Maste2013-07-242-0/+2
| | | | | | | These fail due to: error: Expression can't be run, because there is no JIT compiled function llvm-svn: 187072
* Don't rely on C99 for loop initializers in test caseStefanus Du Toit2013-07-241-2/+4
| | | | | | This allows compilation of the test case with GCC 4.8. llvm-svn: 187057
* <rdar://problem/13779789>Enrico Granata2013-06-112-0/+11
| | | | | | Allow memory read -t to take persistent types (those defined with expression struct $....) llvm-svn: 183766
* Fixes for the IR interpreter:Sean Callanan2013-06-051-0/+3
| | | | | | | | | | | | | | - Implemented the SExt instruction, and - eliminated redundant codepaths for constant handling. Added test cases. <rdar://problem/13244258> <rdar://problem/13955820> llvm-svn: 183344
* Fixed signed operations in the IR interpreter.Sean Callanan2013-05-241-5/+5
| | | | | | | | Scalar now can make itself signed if needed. <rdar://problem/13977632> llvm-svn: 182668
* Fixed a bug where persistent variables did notSean Callanan2013-05-222-11/+17
| | | | | | | | | | | | | | | | | live as long as they needed to. This led to equality tests involving persistent variables often failing or succeeding when they had no business doing so. To do this, I introduced the ability for a memory allocation to "leak" - that is, to persist in the process beyond the lifetime of the expression. Hand-declared persistent variables do this now. <rdar://problem/13956311> llvm-svn: 182528
* Handle the case where there is a user breakpoint set at the location of one ↵Jim Ingham2013-05-161-5/+17
| | | | | | | | | | | of our function call exception catching breakpoints. We need to force ourselves to stop in that case. <rdar://problem/13903801> llvm-svn: 182056
* Clean up linux test decorators and add links to known bugsDaniel Malea2013-05-153-3/+3
| | | | | | | | | - s/skipOnLinux/skipIfLinux/ to match style of every other decorator - linkify bugizilla/PR numbers in comments No intended change in functionality. llvm-svn: 181913
* Add temporary fix for calling c++ global/anonymous functions on Linux.Matt Kopec2013-05-101-1/+0
| | | | llvm-svn: 181613
* Mark tests as expected fail for Linux due to not being able to call/print ↵Matt Kopec2013-04-261-0/+1
| | | | | | c++ demangled functions in the global namespace (bugzilla 15854). llvm-svn: 180623
* Fix test case to not run to main and "next" 5 times. Use a breakpoint.Greg Clayton2013-04-022-13/+18
| | | | llvm-svn: 178552
* Update TestCallStdStringFunction to expected fail for gcc and account for ↵Matt Kopec2013-03-011-2/+3
| | | | | | | | multiple breakpoint locations. Patch from Ashok Thirumurthi. llvm-svn: 176357
* Skip test that fails intermittently with Clang/GCC on LinuxDaniel Malea2013-02-251-1/+1
| | | | | | - was causing buildbot failures due to unexpected pass llvm-svn: 176048
* Linux test case cleanup:Daniel Malea2013-02-153-1/+2
| | | | | | | | | - Enable TestFormatters.py: expressions with "new" work - Enable TestChangeValueAPI.py: llvm.org/PR15039 fixed - Disable expression_command/call-restarts due to llvm.org/PR15278 - Disable expression_command/call-throws due to ObjC test program llvm-svn: 175287
* Add a test for handling a function call that throws an exception, and make ↵Jim Ingham2013-02-143-0/+138
| | | | | | | | it work. <rdar://problem/13183944> llvm-svn: 175127
* Skip tests that assert on Linux in ↵Daniel Malea2013-02-131-1/+1
| | | | | | | | RecordLayoutBuilder::updateExternalFieldOffset() - Filed bugzilla PR-15256 llvm-svn: 175065
* Forgot to add the testsuite for the changes I checked in on Friday.Jim Ingham2013-02-113-0/+212
| | | | llvm-svn: 174897
* Disable confirmation prompts for testingDaniel Malea2013-01-251-0/+5
| | | | | | | - set auto-confirm to false when running TestExprs (avoid hang when using API) - set prompt-on-quit to false in test helper (avoid timeout when using lldb CLI) llvm-svn: 173485
OpenPOWER on IntegriCloud