Skip to content
  1. Sep 09, 2010
  2. Sep 08, 2010
  3. Sep 07, 2010
  4. Sep 04, 2010
    • Caroline Tice's avatar
      · 3df9a8df
      Caroline Tice authored
      This is a very large commit that completely re-does the way lldb
      handles user settable internal variables (the equivalent of set/show
      variables in gdb).  In addition to the basic infrastructure (most of
      which is defined in UserSettingsController.{h,cpp}, there are examples
      of two classes that have been set up to contain user settable
      variables (the Debugger and Process classes).  The 'settings' command
      has been modified to be a command-subcommand structure, and the 'set',
      'show' and 'append' commands have been moved into this sub-commabnd
      structure.  The old StateVariable class has been completely replaced
      by this, and the state variable dictionary has been removed from the
      Command Interpreter.  Places that formerly accessed the state variable
      mechanism have been modified to access the variables in this new
      structure instead (checking the term-width; getting/checking the
      prompt; etc.)
      
      Variables are attached to classes; there are two basic "flavors" of
      variables that can be set: "global" variables (static/class-wide), and
      "instance" variables (one per instance of the class).  The whole thing
      has been set up so that any global or instance variable can be set at
      any time (e.g. on start up, in your .lldbinit file), whether or not
      any instances actually exist (there's a whole pending and default
      values mechanism to help deal with that).
      
      llvm-svn: 113041
      3df9a8df
    • Greg Clayton's avatar
      Improved name demangling performance by 20% on darwin. · e41e5899
      Greg Clayton authored
      llvm-svn: 113032
      e41e5899
    • Greg Clayton's avatar
      Cleaned up step logging a bit. · 1346f7e0
      Greg Clayton authored
      llvm-svn: 113023
      1346f7e0
    • Johnny Chen's avatar
      Fixed an lldb infrastructure bug, where the debugger should reaaly update its · 725945d5
      Johnny Chen authored
      execution context only when the process is still alive.  When running the test
      suite, the debugger is launching and killing processes constantly.
      
      This might be the cause of the test hang as reported in rdar://problem/8377854,
      where the debugger was looping infinitely trying to update a supposedly stale
      thread list.
      
      llvm-svn: 113022
      725945d5
  5. Sep 03, 2010
Loading