Skip to content
  1. Jul 02, 2010
  2. Jul 01, 2010
  3. Jun 30, 2010
  4. Jun 29, 2010
  5. Jun 28, 2010
    • Greg Clayton's avatar
      Added function name types to allow us to set breakpoints by name more · 0c5cd90d
      Greg Clayton authored
      intelligently. The four name types we currently have are:
      
      eFunctionNameTypeFull       = (1 << 1), // The function name.
                                              // For C this is the same as just the name of the function
                                              // For C++ this is the demangled version of the mangled name.
                                              // For ObjC this is the full function signature with the + or
                                              // - and the square brackets and the class and selector
      eFunctionNameTypeBase       = (1 << 2), // The function name only, no namespaces or arguments and no class 
                                              // methods or selectors will be searched.
      eFunctionNameTypeMethod     = (1 << 3), // Find function by method name (C++) with no namespace or arguments
      eFunctionNameTypeSelector   = (1 << 4)  // Find function by selector name (ObjC) names
      
      
      this allows much more flexibility when setting breakoints:
      
      (lldb) breakpoint set --name main --basename
      (lldb) breakpoint set --name main --fullname
      (lldb) breakpoint set --name main --method
      (lldb) breakpoint set --name main --selector
      
      The default:
      
      (lldb) breakpoint set --name main
      
      will inspect the name "main" and look for any parens, or if the name starts
      with "-[" or "+[" and if any are found then a full name search will happen.
      Else a basename search will be the default.
      
      Fixed some command option structures so not all options are required when they
      shouldn't be.
      
      Cleaned up the breakpoint output summary.
      
      Made the "image lookup --address <addr>" output much more verbose so it shows
      all the important symbol context results. Added a GetDescription method to 
      many of the SymbolContext objects for the more verbose output.
      
      llvm-svn: 107075
      0c5cd90d
    • Johnny Chen's avatar
      Added test for a previously fixed bug where invoking lldb command from an emacs · 7e363f55
      Johnny Chen authored
      shell and issuing 'help' would hang (was actually infinitely looping).
      
      llvm-svn: 107066
      7e363f55
  6. Jun 26, 2010
  7. Jun 25, 2010
    • Johnny Chen's avatar
      A simple testing framework for lldb using python's unit testing framework. · a765c28d
      Johnny Chen authored
      Tests for lldb are written as python scripts which take advantage of the script
      bridging provided by LLDB.framework to interact with lldb core.
      
      A specific naming pattern is followed by the .py script to be recognized as
      a module which implements a test scenario, namely, Test*.py.
      
      To specify the directories where "Test*.py" python test scripts are located,
      you need to pass in a list of directory names.  By default, the current
      working directory is searched if nothing is specified on the command line.
      
      An example:
      
      [14:10:20] johnny:/Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v example
      test_choice (TestSequenceFunctions.TestSequenceFunctions) ... ok
      test_sample (TestSequenceFunctions.TestSequenceFunctions) ... ok
      test_shuffle (TestSequenceFunctions.TestSequenceFunctions) ... ok
      
      ----------------------------------------------------------------------
      Ran 3 tests in 0.000s
      
      OK
      
      llvm-svn: 106890
      a765c28d
    • Jim Ingham's avatar
      Remove a reference to Leopard. · e1c8c4b1
      Jim Ingham authored
      llvm-svn: 106814
      e1c8c4b1
  8. Jun 24, 2010
Loading