Kate Stone b9c1b51e45 *** This commit represents a complete reformatting of the LLDB source code
*** to conform to clang-format’s LLVM style.  This kind of mass change has
*** two obvious implications:

Firstly, merging this particular commit into a downstream fork may be a huge
effort.  Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit.  The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):

    find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
    find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;

The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.

Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit.  There are alternatives available that will attempt
to look through this change and find the appropriate prior commit.  YMMV.

llvm-svn: 280751
2016-09-06 20:57:50 +00:00

69 lines
2.4 KiB
Python

"""
Test some lldb command abbreviations.
"""
from __future__ import print_function
import lldb
import os
import time
import lldbsuite.support.seven as seven
from lldbsuite.test.decorators import *
from lldbsuite.test.lldbtest import *
from lldbsuite.test import lldbutil
def execute_command(command):
# print('%% %s' % (command))
(exit_status, output) = seven.get_command_status_output(command)
# if output:
# print(output)
# print('status = %u' % (exit_status))
return exit_status
class FatArchiveTestCase(TestBase):
mydir = TestBase.compute_mydir(__file__)
@skipUnlessDarwin
def test(self):
if self.getArchitecture() == 'x86_64':
execute_command("make CC='%s'" % (os.environ["CC"]))
self.main()
else:
self.skipTest(
"This test requires x86_64 as the architecture for the inferior")
def main(self):
'''This test compiles a quick example by making a fat file (universal) full of
skinny .o files and makes sure we can use them to resolve breakpoints when doing
DWARF in .o file debugging. The only thing this test needs to do is to compile and
set a breakpoint in the target and verify any breakpoint locations have valid debug
info for the function, and source file and line.'''
exe = os.path.join(os.getcwd(), "a.out")
# Create the target
target = self.dbg.CreateTarget(exe)
# Create a breakpoint by name
breakpoint = target.BreakpointCreateByName('foo', exe)
self.assertTrue(breakpoint, VALID_BREAKPOINT)
# Make sure the breakpoint resolves to a function, file and line
for bp_loc in breakpoint:
# Get a section offset address (lldb.SBAddress) from the breakpoint
# location
bp_loc_addr = bp_loc.GetAddress()
line_entry = bp_loc_addr.GetLineEntry()
function = bp_loc_addr.GetFunction()
self.assertTrue(
function.IsValid(),
"Verify breakpoint in fat BSD archive has valid function debug info")
self.assertTrue(
line_entry.GetFileSpec(),
"Verify breakpoint in fat BSD archive has source file information")
self.assertTrue(
line_entry.GetLine() != 0,
"Verify breakpoint in fat BSD archive has source line information")