Get attaching to a crashed Windows process right (CDB).

Handle  the 2nd parameter correctly as a event id
to be used for a handshake. Introduce a special mode
when attaching to crashed processes.
Code cleanup, pass StartParameters along to startDebugger.
This commit is contained in:
Friedemann Kleint
2009-05-26 16:27:24 +02:00
parent af4fcde1c2
commit 09380afe90
14 changed files with 79 additions and 49 deletions

View File

@@ -118,12 +118,13 @@ enum DebuggerStatus
enum DebuggerStartMode
{
StartInternal, // Start current start project's binary
StartExternal, // Start binary found in file system
AttachExternal, // Attach to running process
AttachTcf, // Attach to a running Target Communication Framework agent
AttachCore, // Attach to a core file
StartRemote // Start and attach to a remote process
StartInternal, // Start current start project's binary
StartExternal, // Start binary found in file system
AttachExternal, // Attach to running process by process id
AttachCrashedExternal, // Attach to crashed process by process id
AttachTcf, // Attach to a running Target Communication Framework agent
AttachCore, // Attach to a core file
StartRemote // Start and attach to a remote process
};
struct DebuggerStartParameters {
@@ -138,6 +139,7 @@ struct DebuggerStartParameters {
QString buildDir;
qint64 attachPID;
bool useTerminal;
QString crashParameter; // for AttachCrashedExternal
// for remote debugging
QString remoteChannel;
QString remoteArchitecture;