summaryrefslogtreecommitdiffstats
path: root/lldb/test/expression_command
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
* Separated the "expr --unwind-on-error" behavior into two parts, actual ↵Jim Ingham2013-01-152-1/+27
| | | | | | | | | | | | | | | | errors (i.e. crashes) which continue to be controlled by the --unwind-on-error flag, and --ignore-breakpoint which separately controls behavior when a called function hits a breakpoint. For breakpoints, we don't unwind, we either stop, or ignore the breakpoint, which makes more sense. Also make both these behaviors globally settable through "settings set". Also handle the case where a breakpoint command calls code that ends up re-hitting the breakpoint. We were recursing and crashing. Now we just stop without calling the second command. <rdar://problem/12986644> <rdar://problem/9119325> llvm-svn: 172503
* <rdar://problem/12028723>Enrico Granata2013-01-092-5/+5
| | | | | | | | | | Adding useful formatting options to the expression (expr) command. As a side effect of this change, the -d option now supports the same three-values enumeration that frame variables uses (run, don't run, none) instead of a boolean like it did previously These options do not apply to print, p or po because these are aliased to not take any options. In order to use them, use expression or expr. llvm-svn: 171993
* Mark TestExprHelpExamples.py as expected to fail on Linux Daniel Malea2013-01-041-0/+1
| | | | | | | - requires memory allocation during expression evaluation - opened related bugzilla 14805 llvm-svn: 171547
* Fix Test11588.py on Linux. The test was failing because the synthetic type ↵Andrew Kaylor2012-12-071-2/+2
| | | | | | fields were resolving to int instead of long. A similar change was made in r155144 to eliminate the type specification for an earlier check in this test, so it seemed appropriate here too. llvm-svn: 169615
* <rdar://problem/12798131> Greg Clayton2012-12-041-3/+3
| | | | | | | | | | | | Cleaned up the option parsing code to always pass around the short options as integers. Previously we cast this down to "char" and lost some information. I recently added an assert that would detect duplicate short character options which was firing during the test suite. This fix does the following: - make sure all short options are treated as "int" - make sure that short options can be non-printable values when a short option is not required or when an option group is mixed into many commands and a short option is not desired - fix the help printing to "do the right thing" in all cases. Previously if there were duplicate short character options, it would just not emit help for the duplicates - fix option parsing when there are duplicates to parse options correctly. Previously the option parsing, when done for an OptionGroup, would just start parsing options incorrectly by omitting table entries and it would end up setting the wrong option value llvm-svn: 169189
* Mark expected failures on Linux (due to bugzilla #14437)Daniel Malea2012-11-272-0/+2
| | | | llvm-svn: 168727
* Skip objC test on non-darwin platformsDaniel Malea2012-11-231-0/+1
| | | | llvm-svn: 168531
* Linux test case fixesDaniel Malea2012-11-211-1/+1
| | | | | | | | - missing includes in cpp test programs - mismatched dwarf/dsym test cases - make "com.apple.main-thread" expected string conditional on darwin platform llvm-svn: 168452
* Fix incorrect usage of buildDsym() in dwarf testDaniel Malea2012-11-201-1/+1
| | | | llvm-svn: 168371
* Fix typo (dwarf/dsym mismatch) in testcase causing early failure on LinuxDaniel Malea2012-11-121-1/+1
| | | | llvm-svn: 167771
* Reverting unwanted changes to the test suiteEnrico Granata2012-10-241-1/+1
| | | | llvm-svn: 166627
* Reverting the changes to Scalar since this class needs to follow C rules for ↵Enrico Granata2012-10-241-1/+1
| | | | | | type promotion llvm-svn: 166626
* <rdar://problem/12462048>Greg Clayton2012-10-171-2/+2
| | | | | | | | | | | | | | | | | | | LLDB changes argv[0] when debugging a symlink. Now we have the notion of argv0 in the target settings: target.arg0 (string) = There is also the program argument that are separate from the first argument that have existed for a while: target.run-args (arguments) = When running "target create <exe>", we will place the untouched "<exe>" into target.arg0 to ensure when we run, we run with what the user typed. This has been added to the ProcessLaunchInfo and all other needed places so we always carry around the: - resolved executable path - argv0 - program args Some systems may not support separating argv0 from the resolved executable path and the ProcessLaunchInfo needs to carry all of this information along so that each platform can make that decision. llvm-svn: 166137
* API cleanup.Greg Clayton2012-10-161-2/+2
| | | | llvm-svn: 166070
* Add the ability to set timeout & "run all threads" options both from the ↵Jim Ingham2012-10-163-0/+140
| | | | | | | | | | "expr" command and from the SB API's that evaluate expressions. <rdar://problem/12457211> llvm-svn: 166062
* Fix all the test case breakages caused by folks writing tests all over the ↵Jim Ingham2012-09-228-33/+12
| | | | | | | | place that depended explicitly on the output of "break set". Please don't do this sort of thing!!!!! llvm-svn: 164433
* Initial commit of a new testsuite feature: test categories.Enrico Granata2012-09-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | This feature allows us to group test cases into logical groups (categories), and to only run a subset of test cases based on these categories. Each test-case can have a new method getCategories(self): which returns a list of strings that are the categories to which the test case belongs. If a test-case does not provide its own categories, we will look for categories in the class that contains the test case. If that fails too, the default implementation looks for a .category file, which contains a comma separated list of strings. The test suite will recurse look for .categories up until the top level directory (which we guarantee will have an empty .category file). The driver dotest.py has a new --category <foo> option, which can be repeated, and specifies which categories of tests you want to run. (example: ./dotest.py --category objc --category expression) All tests that do not belong to any specified category will be skipped. Other filtering options still exist and should not interfere with category filtering. A few tests have been categorized. Feel free to categorize others, and to suggest new categories that we could want to use. All categories need to be validly defined in dotest.py, or the test suite will refuse to run when you use them as arguments to --category. In the end, failures will be reported on a per-category basis, as well as in the usual format. This is the very first stage of this feature. Feel free to chime in with ideas for improvements! llvm-svn: 164403
* Make issue_11588/Test11588 work with a recent swig that converts ints to ↵Filipe Cabecinhas2012-05-111-2/+2
| | | | | | PyLongObjects llvm-svn: 156637
* Made it safe to re-import a Python module, allowingSean Callanan2012-04-251-1/+1
| | | | | | | the same test to be run multiple times in the same session. llvm-svn: 155511
* Removing the @expectedFailurei386 decorator from test cases that now work as ↵Enrico Granata2012-04-242-4/+0
| | | | | | a result of the latest changes to Value.cpp llvm-svn: 155419
* Not a test failure for i386; instead, the test case should be modified to ↵Johnny Chen2012-04-191-3/+2
| | | | | | | | not over-expect type fields for the synthetic childs. rdar://problem/11277013 llvm-svn: 155144
* Add expected failure decorators for test cases which are failing for i386 ↵Johnny Chen2012-04-194-0/+6
| | | | | | | | architecture. Plus fix some test cases to skip/succeed for i386. llvm-svn: 155087
OpenPOWER on IntegriCloud