Skip to content
  • Greg Clayton's avatar
    Moved the execution context that was in the Debugger into · 8b82f087
    Greg Clayton authored
    the CommandInterpreter where it was always being used.
    
    Make sure that Modules can track their object file offsets correctly to
    allow opening of sub object files (like the "__commpage" on darwin).
    
    Modified the Platforms to be able to launch processes. The first part of this
    move is the platform soon will become the entity that launches your program
    and when it does, it uses a new ProcessLaunchInfo class which encapsulates
    all process launching settings. This simplifies the internal APIs needed for
    launching. I want to slowly phase out process launching from the process
    classes, so for now we can still launch just as we used to, but eventually
    the platform is the object that should do the launching.
    
    Modified the Host::LaunchProcess in the MacOSX Host.mm to correctly be able
    to launch processes with all of the new eLaunchFlag settings. Modified any
    code that was manually launching processes to use the Host::LaunchProcess
    functions.
    
    Fixed an issue where lldb_private::Args had implicitly defined copy 
    constructors that could do the wrong thing. This has now been fixed by adding
    an appropriate copy constructor and assignment operator.
    
    Make sure we don't add empty ModuleSP entries to a module list.
    
    Fixed the commpage module creation on MacOSX, but we still need to train
    the MacOSX dynamic loader to not get rid of it when it doesn't have an entry
    in the all image infos.
    
    Abstracted many more calls from in ProcessGDBRemote down into the 
    GDBRemoteCommunicationClient subclass to make the classes cleaner and more
    efficient.
    
    Fixed the default iOS ARM register context to be correct and also added support
    for targets that don't support the qThreadStopInfo packet by selecting the
    current thread (only if needed) and then sending a stop reply packet.
    
    Debugserver can now start up with a --unix-socket (-u for short) and can 
    then bind to port zero and send the port it bound to to a listening process
    on the other end. This allows the GDB remote platform to spawn new GDB server
    instances (debugserver) to allow platform debugging.
    
    llvm-svn: 129351
    8b82f087
Loading