summaryrefslogtreecommitdiffstats
path: root/lldb/test/functionalities/data-formatter
Commit message (Collapse)AuthorAgeFilesLines
...
* [TestFormatters, TestDataFormatterSynthVal] Mark as xfail.Siva Chandra2015-04-101-0/+1
| | | | | | | | | | | | | | | | Summary: This is to get the bots to go green while a robust solution to fix these tests is worked out. Reviewers: chaoren, tberghammer, clayborg Reviewed By: tberghammer, clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8947 llvm-svn: 234625
* Add missing makefile got test caseTamas Berghammer2015-04-011-0/+4
| | | | llvm-svn: 233797
* Enabled a bunch of tests on LinuxVince Harron2015-03-312-5/+0
| | | | | | | | | Removed expectedFailureLinux from failures that I was unable to reproduce, updated and improved some other comments near XFAIL tests Differential Revision: http://reviews.llvm.org/D8676 llvm-svn: 233716
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-3051-89/+89
| | | | | | | | | | | | | | | | against remote platform. Adds @skipIfPlatform and @skipUnlessPlatform decorators which will skip if / unless the target platform is in the provided platform list. Test Plan: ninja check-lldb shows no regressions. When running cross platform, tests which cannot run on the target platform are skipped. Differential Revision: http://reviews.llvm.org/D8665 llvm-svn: 233547
* Fix StdVBoolImplementation to handle large vectorsTamas Berghammer2015-03-251-1/+0
| | | | | | | | | | The previous implementation only read out the first element of the underlying storage array. Because of it only the first 32 (on x86) or the first 64 (on x86_64) element was displayed. Differential revision: http://reviews.llvm.org/D8585 llvm-svn: 233179
* xfail tests that failed with clang-3.7, gcc4.8.2 and on i386 to get buildbot ↵Ying Chen2015-03-251-0/+1
| | | | | | | | | | | | | | | | | | green Summary: -Refer to bug https://buganizer.corp.google.com/issues/19893563 -Test log http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/1145 Test Plan: Run tests with different compiler and archs locally Reviewers: sivachandra, ovyalov, chaoren, vharron Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D8573 llvm-svn: 233157
* [TestDataFormatterStdVector] s/-fstandalone-debug/-fno-limit-debug-infoSiva Chandra2015-03-241-3/+3
| | | | | | | | | | | | Test Plan: dotest.py -C <clang|gcc> -p TestDataFormatterStdVector Reviewers: vharron Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8571 llvm-svn: 233108
* Fix error introduced by changing function signatures.Zachary Turner2015-03-242-1/+2
| | | | | | | | | | | | | | | | | Since ClangASTSource::layoutRecordType() was overriding a virtual function in the base, this was inadvertently causing a new method to be introduced rather than an override. To fix this all method signatures are changed back to taking DenseMaps, and the `override` keyword is added to make sure this type of error doesn't happen again. To keep the original fix intact, which is that fields and bases must be added in offset order, the ImportOffsetMap() function now copies the DenseMap into a vector and then sorts the vector on the value type (e.g. the offset) before iterating over the sorted vector and inserting the items. llvm-svn: 233099
* Fix record layout when synthesizing class types.Zachary Turner2015-03-242-2/+1
| | | | | | | | | | | | | | | | | Prior to this patch, we would try to synthesize class types by iterating over a DenseMap of FieldDecls and adding each one to a CXXRecordDecl. Since a DenseMap doesn't provide a deterministic ordering of the elements, this would not add the fields in FieldOffset order, but rather in some random order determined by the memory layout of the DenseMap. This patch fixes the issue by changing DenseMaps to vectors. The ability to lookup a value in the DenseMap was hardly being used, and where it is sufficient to do a vector lookup. Differential Revision: http://reviews.llvm.org/D8512 llvm-svn: 233090
* Don't clobber CFLAGS_EXTRAS in tests.Robert Flack2015-03-249-10/+10
| | | | | | | | | | | | | | | | | To run tests against a different target platform many extra compiler flags are needed to specify sysroot, include dirs, etc. The environment variable CFLAGS_EXTRAS seems suited for this purpose except that several Makefiles clobber the current flags. This change modifies all of these to add to CFLAGS_EXTRAS instead. Test Plan: Verify no regressions in ninja check-lldb. Run tests using CFLAGS_EXTRAS to specify cross compilation flags for a different target running lldb-server platform. Differential Revision: http://reviews.llvm.org/D8559 llvm-svn: 233066
* Fix ObjCDataFormatterTestCase.test_nsdate_* tests (ver. 2)Ilia K2015-03-232-3/+3
| | | | | | This commit reverts r232946 because it caused an another error with absolute time. llvm-svn: 232951
* Fix ObjCDataFormatterTestCase.test_nsdate_* testsIlia K2015-03-231-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The time/date strings (like "6pm April 10, 1985") are interpreted as a local time but CFDateGetAbsoluteTime() returns time in UTC. It caused a problem when local time was UTC+0100 or more (0200, 0300 etc.): ``` ====================================================================== FAIL: test_nsdate_with_dsym_and_run_command (TestDataFormatterObjC.ObjCDataFormatterTestCase) Test formatters for NSDate. ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 462, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/data-formatter-objc/TestDataFormatterObjC.py", line 157, in test_nsdate_with_dsym_and_run_command self.appkit_tester_impl(self.buildDsym,self.nsdate_data_formatter_commands) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/data-formatter-objc/TestDataFormatterObjC.py", line 34, in appkit_tester_impl commands() File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/data-formatter-objc/TestDataFormatterObjC.py", line 475, in nsdate_data_formatter_commands substrs = ['1985-04','2011-01']) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 2146, in expect msg if msg else EXP_MSG(str, exe)) AssertionError: False is not True : '2011-01' returns expected result Config=x86_64-clang ====================================================================== FAIL: test_nsdate_with_dwarf_and_run_command (TestDataFormatterObjC.ObjCDataFormatterTestCase) Test formatters for NSDate. ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 479, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/data-formatter-objc/TestDataFormatterObjC.py", line 163, in test_nsdate_with_dwarf_and_run_command self.appkit_tester_impl(self.buildDwarf,self.nsdate_data_formatter_commands) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/data-formatter-objc/TestDataFormatterObjC.py", line 34, in appkit_tester_impl commands() File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/data-formatter-objc/TestDataFormatterObjC.py", line 475, in nsdate_data_formatter_commands substrs = ['1985-04','2011-01']) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 2146, in expect msg if msg else EXP_MSG(str, exe)) AssertionError: False is not True : '2011-01' returns expected result Config=x86_64-clang ``` llvm-svn: 232946
* Cleanup to simplify the formatter for std::map of libstdc++.Siva Chandra2015-03-181-2/+0
| | | | | | | | | | | | | | | | | | Summary: GCC does not emit some DWARF required for the simplified formatter to work. A workaround for it has been incorporated in the formatter. The corresponding test TestDataFormatterStdMap has also been enabled for GCC. Test Plan: dotest.py -C <clang|gcc> -p TestDataFormatterStdMap Reviewers: clayborg, vharron, granata.enrico Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8424 llvm-svn: 232678
* Enable TestDataFormatterStdIterator with GCC.Siva Chandra2015-03-171-1/+0
| | | | | | | | | | | | | | | | | Summary: This test now passes for Clang and GCC. I do not know why it was disabled for GCC with link to a bug which should not have had an effect on this test. Test Plan: dotest.py -C gcc -p TestDataFormatterStdIterator Reviewers: vharron Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8396 llvm-svn: 232552
* Implement formatter for std::vector<bool, ...> of libstdc++ in Python.Siva Chandra2015-03-171-5/+0
| | | | | | | | | | | | | | | | | | | Summary: The existing formatter in C++ has been removed as it was not being used. The associated test TestDataFormatterStdVBool.py has been enabled for both Clang and GCC on Linux. Test Plan: dotest.py -p TestDataFormatterStdVBool Reviewers: vharron, clayborg Reviewed By: clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8390 llvm-svn: 232548
* Enable TestDataFormatterStdMap on linux (libstdc++) with clang.Siva Chandra2015-03-162-4/+7
| | | | | | | | | | | | | | | | | | | | | Summary: This test should have been enabled along with 7181dae1248cc1b03505cca1b7c6e3dfeffefc0a, but since the test was actually crashing, I thought it was a much deeper problem. Turns out, all I had to do was to add "-fno-limit-debug-info" when compiling the test case. The test is still skipped when the testcase is compiled with GCC. Test Plan: dotest.py -p TestDataFormatterStdMap Reviewers: vharron Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8364 llvm-svn: 232432
* Skip TestDataFormatterStdMap on linux instead of xfailing.Siva Chandra2015-03-161-4/+4
| | | | | | | | | | | | | | | | Summary: After 7181dae1248cc1b03505cca1b7c6e3dfeffefc0a, this test progresses much further but crashes. Will skip this test while I fix this properly. Test Plan: dotest.py -p TestDataFormatterStdMap Reviewers: vharron Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8361 llvm-svn: 232403
* Handle PyLong return values in LLDBSwigPython_CalculateNumChildren.Siva Chandra2015-03-163-9/+7
| | | | | | | | | | | | | | | | | | | | | | Summary: Also, change its return type to size_t to match the return types of its callers. With this change, std::vector and std::list data formatter tests pass on Linux (when using libstdc++) with clang as well as with gcc. These tests have also been enabled in this patch. Test Plan: dotest.py -p <TestDataFormatterStdVector|TestDataFormatterStdList> Reviewers: vharron, clayborg Reviewed By: clayborg Subscribers: zturner, lldb-commits Differential Revision: http://reviews.llvm.org/D8337 llvm-svn: 232399
* Use -fno-limit-debug-info instead of -fstandalone-debug in testsVince Harron2015-03-157-7/+7
| | | | | | | | | | | | | This fixes tests on clang-3.4 AFAICT, these flags have the same affect and -fstandalone-debug wasn't added until after clang-3.4 Committed to try to fix buildbot Differential Revision: http://reviews.llvm.org/D8347 llvm-svn: 232326
* Skip VectorTypesFormatting test case when using gccTamas Berghammer2015-03-131-0/+1
| | | | | | Gcc don't support the ext_vector_type extension used by the test llvm-svn: 232169
* Fix expectation in TestDataFormatterSynthTamas Berghammer2015-03-131-1/+1
| | | | | | | | | The value of some_values (pointer) expeced to start by 0x0 but nothing requires that the first digit of the address be '0'. This CL change the expectation to check only for a value starting with 0x. llvm-svn: 232163
* Fix a bug in the data formatters where summary strings would not look into ↵Enrico Granata2015-03-121-2/+0
| | | | | | | | the non-synthetic value for child members if the ValueObject being formatted happened to have a synthetic value rdar://15630776 llvm-svn: 232114
* A few improvements to our vector types formatting story:Enrico Granata2015-03-062-6/+6
| | | | | | | | | - use a hardcoded formatter to match all vector types, and make it so that their element type is taken into account when doing default formatting - special case a vector of char to display byte values instead of characters by default Fixes the test failures Ilia was seeing llvm-svn: 231504
* Fix Radar10642615DataFormatterTestCase after r231449Ilia K2015-03-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: I'm not sure that this failure should be fixed by modifying this test. It seems strange for me that the only one type vUInt8 is printed with '0x' prefix. This patch fixes the following error: ``` ====================================================================== FAIL: test_with_dsym_and_run_command (Test-rdar-10642615.Radar10642615DataFormatterTestCase) Test data formatter commands. ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 456, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/rdar-10642615/Test-rdar-10642615.py", line 21, in test_with_dsym_and_run_command self.data_formatter_commands() File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/rdar-10642615/Test-rdar-10642615.py", line 68, in data_formatter_commands '(vBool32) valueBool32 = (0, 1, 0, 1)']) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 2100, in expect msg if msg else EXP_MSG(str, exe)) AssertionError: False is not True : '(vUInt8) valueU8 = ('\x01', '\0', '\x04', '\0', '\0', '\x01', '\0', '\x04', '\0', '\0', '\0', '\0', '\0', '\0', '\0', '\0')' returns expected result Config=x86_64-clang ====================================================================== FAIL: test_with_dwarf_and_run_command (Test-rdar-10642615.Radar10642615DataFormatterTestCase) Test data formatter commands. ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 473, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/rdar-10642615/Test-rdar-10642615.py", line 28, in test_with_dwarf_and_run_command self.data_formatter_commands() File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/data-formatter/rdar-10642615/Test-rdar-10642615.py", line 68, in data_formatter_commands '(vBool32) valueBool32 = (0, 1, 0, 1)']) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 2100, in expect msg if msg else EXP_MSG(str, exe)) AssertionError: False is not True : '(vUInt8) valueU8 = ('\x01', '\0', '\x04', '\0', '\0', '\x01', '\0', '\x04', '\0', '\0', '\0', '\0', '\0', '\0', '\0', '\0')' returns expected result Config=x86_64-clang ---------------------------------------------------------------------- ``` Reviewers: granata.enrico, zturner, clayborg Subscribers: clayborg, lldb-commits, zturner, granata.enrico Differential Revision: http://reviews.llvm.org/D8102 llvm-svn: 231490
* Provide synthetic children for some vector typesEnrico Granata2015-03-063-0/+100
| | | | | | | | | | Unlike GDB, we tackle the problem of representing vector types in different styles by having a synthetic child provider that recognizes the format you're trying to apply to the variable, and coming up with the right type and number of child values to match that format This makes for a more compact representation and less visual noise Fixes rdar://5429347 llvm-svn: 231449
* Use -fstandalone-debug for few tests to get around a Clang optimizationVince Harron2015-02-287-0/+50
| | | | | | | | | | | | | | | | | | | clang-3.5+ outputs FullDebugInfo by default for Darwin/FreeBSD targets. Other targets do not, which causes several tests to fail. This flag enables FullDebugInfo for all targets. Fixes the following tests: TestCallStdStringFunction.py TestDataFormatterSkipSummary.py TestDataFormatterStdIterator.py TestDataFormatterStdList.py TestDataFormatterStdString.py TestSBValuePersist.py TestStringPrinter.py TestTypeCompletion.py llvm-svn: 230831
* Revert "Revert "I had recently added a new SBFrame::GetVariables() overload ↵Zachary Turner2015-02-171-4/+0
| | | | | | | | | | | with yet another bool argument"" Reverting this commit led to other failures which I did not see at first. This turned out to be an easy problem to fix, so I added SBVariablesOptions.cpp to the CMakeLists.txt. In the future please try to make sure new files are added to CMake. llvm-svn: 229516
* Revert "I had recently added a new SBFrame::GetVariables() overload with yet ↵Zachary Turner2015-02-171-0/+4
| | | | | | | | | | | | | | another bool argument" This reverts commit r228975. It was causing link errors on the Windows bots, since last Thursday. http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc/builds/725 Conflicts: lldb.xcodeproj/project.pbxproj llvm-svn: 229514
* I had recently added a new SBFrame::GetVariables() overload with yet another ↵Enrico Granata2015-02-121-4/+0
| | | | | | | | | | bool argument We talked about it internally - and came to the conclusion that it's time to have an options class This commit adds an SBVariablesOptions class and goes through all the required dance llvm-svn: 228975
* Re-add makefiles of inline testsPavel Labath2015-02-122-0/+8
| | | | llvm-svn: 228925
* Add a JSON producer to LLDB - this is a set of classes that encapsulate JSON ↵Enrico Granata2015-02-102-8/+0
| | | | | | | | objects and allow you to write them to a Stream for subsequent processing Using this JSON producer, write a little tool that expands its own command-line arguments and dumps them to stdout as a JSON array llvm-svn: 228636
* Check-in generated test makefilesPavel Labath2015-02-053-0/+12
| | | | | | for rationale, see D7407. llvm-svn: 228314
* Get rid of Debugger::FormatPrompt() and replace it with the new FormatEntity ↵Greg Clayton2015-02-042-2/+2
| | | | | | | | | | | | | | | | | | | class. Why? Debugger::FormatPrompt() would run through the format prompt every time and parse it and emit it piece by piece. It also did formatting differently depending on which key/value pair it was parsing. The new code improves on this with the following features: 1 - Allow format strings to be parsed into a FormatEntity::Entry which can contain multiple child FormatEntity::Entry objects. This FormatEntity::Entry is a parsed version of what was previously always done in Debugger::FormatPrompt() so it is more efficient to emit formatted strings using the new parsed FormatEntity::Entry. 2 - Allows errors in format strings to be shown immediately when setting the settings (frame-format, thread-format, disassembly-format 3 - Allows auto completion by implementing a new OptionValueFormatEntity and switching frame-format, thread-format, and disassembly-format settings over to using it. 4 - The FormatEntity::Entry for each of the frame-format, thread-format, disassembly-format settings only replaces the old one if the format parses correctly 5 - Combines all consecutive string values together for efficient output. This means all "${ansi.*}" keys and all desensitized characters like "\n" "\t" "\0721" "\x23" will get combined with their previous strings 6 - ${*.script:} (like "${var.script:mymodule.my_var_function}") have all been switched over to use ${script.*:} "${script.var:mymodule.my_var_function}") to make the format easier to parse as I don't believe anyone was using these format string power user features. 7 - All key values pairs are defined in simple C arrays of entries so it is much easier to add new entries. These changes pave the way for subsequent modifications where we can modify formats to do more (like control the width of value strings can do more and add more functionality more easily like string formatting to control the width, printf formats and more). llvm-svn: 228207
* Skip Objective-C test on non-Darwin platformsEd Maste2015-01-301-1/+2
| | | | llvm-svn: 227578
* Add an overload of SetValueFromCString() to ValueObjectSynthetic that is ↵Enrico Granata2015-01-263-0/+26
| | | | | | | | | | just a passthrough to the parent object Without this overload, attempts to edit the value of a variable with synthetic children enabled would change the value inside the synthetic ValueObject, but not propagate the changes to the underlying storage, hence resulting in no write for any meaningful purpose Comes with a test case, and fixes rdar://19586311 llvm-svn: 227120
* Replace more runCmd('continue') with process control API.Enrico Granata2015-01-223-24/+24
| | | | llvm-svn: 226860
* Speed these tests up quite significantly by using the SB API instead of ↵Enrico Granata2015-01-216-52/+26
| | | | | | | | running the "continue" command at each step The reason why one mechanism is so much faster than the other (as in, ~10 seconds vs. ~1 minute) is quite baffling to me at the moment, but these are not process handling tests, so do what's faster llvm-svn: 226730
* Disable data formatter tests on Windows.Zachary Turner2014-12-102-0/+2
| | | | | | | | | | clang does not yet support MS-ABI record layout for externally-sourced ASTs. As a result, attempting to format something that requires data layout results in undefined behavior in clang, in this case an assert. http://llvm.org/pr21800 tracks fixing this on the clang side. llvm-svn: 223868
* Mark 9 lldb unit tests for ubuntu as XFAIL.Siva Chandra2014-11-225-2/+21
| | | | | | | | | | | | | | | | | | | | The following lldb unit tests fail check-lldb on ubuntu: TestDataFormatterStdMap.py TestDataFormatterStdVBool.py TestDataFormatterStdVector.py TestDataFormatterSynthVal.py TestEvents.py TestInitializerList.py TestMemoryHistory.py TestReportData.py TestValueVarUpdate.py These unit test failures are for non-core functionality. The intent is to reduce the check-lldb FAILS to core functionality FAILS and then circle back later and fix these FAILS at a later date. llvm-svn: 222608
* Shuffle APIs around a little bit, so that if you pass custom summary ↵Enrico Granata2014-11-181-1/+8
| | | | | | options, we don't end up caching the summary hence obtained. You may want to obtain an uncapped summary, but this should not be reflected in the summary we cache. The drawback is that we don't cache as aggressively as we could, but at least you get to have different summaries with different options without having to reset formatters or the SBValue at each step llvm-svn: 222280
* Add the ability for the NSString and libc++ std::string formatters to ↵Enrico Granata2014-11-182-1/+8
| | | | | | retrieve uncapped data llvm-svn: 222277
* Move a bunch of summary formatters to oneliner mode. This makes more cases ↵Enrico Granata2014-11-111-10/+8
| | | | | | eligible for oneline printing, and fixes rdar://18120906 llvm-svn: 221701
* Allow inline test case to register actually useful teardown hooks by ↵Enrico Granata2014-11-051-3/+1
| | | | | | allowing a hook to be passed back the test instance, were it not to be already bound to self. Use this ability to make the reversal of escape-non-printables a teardown hook for added reliability of the testing logic llvm-svn: 221402
* Add a setting escape-non-printables that drives whether the StringPrinter ↵Enrico Granata2014-11-052-0/+26
| | | | | | | | | | | should or should not escape sequences such as \t, \n, .. and generally any non-printing character The recent StringPrinter changes made this behavior the default, and the setting defaults to yes If you want to change this behavior and see non-printables unescaped (e.g. "a\tb" as "a b"), set it to false Fixes rdar://12969594 llvm-svn: 221399
* Add a feature where a string data formatter can now be partially composed of ↵Enrico Granata2014-10-284-0/+89
| | | | | | | | | | | | | | Python summary functions This works similarly to the {thread/frame/process/target.script:...} feature - you write a summary string, part of which is ${var.script:someFuncName} someFuncName is expected to be declared as def someFuncName(SBValue,otherArgument) - essentially the same as a summary function Since . -> [] are the only allowed separators, and % is used for custom formatting, .script: would not be a legitimate symbol anyway, which makes this non-ambiguous llvm-svn: 220821
* When trying to get the element type of an array type, do not go to the ↵Enrico Granata2014-10-282-0/+17
| | | | | | canonical type, since that will strip typedefs where we want them to be preserved. Fixes rdar://15453076 llvm-svn: 220810
* Reorganize some of the data formatters code to simplify ↵Enrico Granata2014-10-222-0/+24
| | | | | | CXXFormattersFunction.h. Also, add a synthetic child provider for libc++'s version of std::initializer_list<T> llvm-svn: 220421
* Fix a problem where summary strings could not use a synthetically generated ↵Enrico Granata2014-10-222-0/+12
| | | | | | value as part of themselves llvm-svn: 220414
* Make this test case more resilient in the face of line-table and inlining ↵Enrico Granata2014-10-152-22/+16
| | | | | | changes llvm-svn: 219828
* If a ValueObject has a child that vends synthetic children, but only does so ↵Enrico Granata2014-10-092-1/+4
| | | | | | to generate a value for itself, that's not a disqualifier from one-line printing. Also, fetch synthetic values if available and requested for children as well while printing them llvm-svn: 219427
OpenPOWER on IntegriCloud