llvm-project/lldb/test/lang/c/strings/TestCStrings.py
Enrico Granata 9128ee2f7a Redesign of the interaction between Python and frozen objects:
- introduced two new classes ValueObjectConstResultChild and ValueObjectConstResultImpl: the first one is a ValueObjectChild obtained from
   a ValueObjectConstResult, the second is a common implementation backend for VOCR and VOCRCh of method calls meant to read through pointers stored
   in frozen objects ; now such reads transparently move from host to target as required
 - as a consequence of the above, removed code that made target-memory copies of expression results in several places throughout LLDB, and also
   removed code that enabled to recognize an expression result VO as such
 - introduced a new GetPointeeData() method in ValueObject that lets you read a given amount of objects of type T from a VO
   representing a T* or T[], and doing dereferences transparently
   in private layer it returns a DataExtractor ; in public layer it returns an instance of a newly created lldb::SBData
 - as GetPointeeData() does the right thing for both frozen and non-frozen ValueObject's, reimplemented ReadPointedString() to use it
   en lieu of doing the raw read itself
 - introduced a new GetData() method in ValueObject that lets you get a copy of the data that backs the ValueObject (for pointers,
   this returns the address without any previous dereferencing steps ; for arrays it actually reads the whole chunk of memory)
   in public layer this returns an SBData, just like GetPointeeData()
 - introduced a new CreateValueFromData() method in SBValue that lets you create a new SBValue from a chunk of data wrapped in an SBData
   the limitation to remember for this kind of SBValue is that they have no address: extracting the address-of for these objects (with any
   of GetAddress(), GetLoadAddress() and AddressOf()) will return invalid values
 - added several tests to check that "p"-ing objects (STL classes, char* and char[]) will do the right thing
Solved a bug where global pointers to global variables were not dereferenced correctly for display
New target setting "max-string-summary-length" gives the maximum number of characters to show in a string when summarizing it, instead of the hardcoded 128
Solved a bug where the summary for char[] and char* would not be shown if the ValueObject's were dumped via the "p" command
Removed m_pointers_point_to_load_addrs from ValueObject. Introduced a new m_address_type_of_children, which each ValueObject can set to tell the address type
 of any pointers and/or references it creates. In the current codebase, this is load address most of the time (the only notable exception being file
 addresses that generate file address children UNLESS we have a live process)
Updated help text for summary-string
Fixed an issue in STL formatters where std::stlcontainer::iterator would match the container's synthetic children providers
Edited the syntax and help for some commands to have proper argument types

llvm-svn: 139160
2011-09-06 19:20:51 +00:00

67 lines
2.1 KiB
Python

"""
Tests that C strings work as expected in expressions
"""
from lldbtest import *
class CStringsTestCase(TestBase):
mydir = os.path.join("lang", "c", "strings")
@unittest2.skipUnless(sys.platform.startswith("darwin"), "requires Darwin")
def test_with_dsym_and_run_command(self):
"""Tests that C strings work as expected in expressions"""
self.buildDsym()
self.static_method_commands()
def test_with_dwarf_and_run_command(self):
"""Tests that C strings work as expected in expressions"""
self.buildDwarf()
self.static_method_commands()
def setUp(self):
TestBase.setUp(self)
def set_breakpoint(self, line):
self.expect("breakpoint set -f main.c -l %d" % line,
BREAKPOINT_CREATED,
startstr = "Breakpoint created")
def static_method_commands(self):
"""Tests that C strings work as expected in expressions"""
self.runCmd("file a.out", CURRENT_EXECUTABLE_SET)
self.set_breakpoint(line_number('main.c', '// breakpoint 1'))
self.runCmd("process launch", RUN_SUCCEEDED)
self.expect("expression -- a[2]",
patterns = ["\((const )?char\) \$0 = 'c'"])
self.expect("expression -- z[2]",
startstr = "(const char) $1 = 'x'")
self.expect("expression -- (int)strlen(\"hello\")",
startstr = "(int) $2 = 5")
self.expect("expression -- \"world\"[2]",
startstr = "(const char) $3 = 'r'")
self.expect("expression -- \"\"[0]",
startstr = "(const char) $4 = '\\0'")
self.expect("p \"hello\"",
substrs = ['(const char [6]) $', 'hello',
'(const char) [0] = \'h\'',
'(const char) [5] = \'\\0\''])
self.expect("p (char*)\"hello\"",
substrs = ['(char *) $', ' = 0x',
'hello'])
if __name__ == '__main__':
import atexit
lldb.SBDebugger.Initialize()
atexit.register(lambda: lldb.SBDebugger.Terminate())
unittest2.main()