Debugger: Sanitize Datatypes, part 3: Address of watch items.

Use a quint64 as address. Split apart special handling of
QAbstractItemModels of old shared-library based dumpers
(passing '$'+ special expression as address) into separate
dumperFlags QByteArray.
This commit is contained in:
Friedemann Kleint
2010-09-22 11:19:35 +02:00
parent 0f823e9e9e
commit b67c1a7889
8 changed files with 88 additions and 47 deletions

View File

@@ -66,7 +66,8 @@ public:
void setType(const QByteArray &, bool guessChildrenFromType = true);
void setValueToolTip(const QString &);
void setError(const QString &);
void setAddress(const QByteArray &);
void setAddress(const quint64 &);
void setHexAddress(const QByteArray &a);
bool isSomethingNeeded() const { return state & NeededMask; }
void setAllNeeded() { state = NeededMask; }
@@ -102,6 +103,7 @@ public:
bool isEqual(const WatchData &other) const;
quint64 coreAddress() const;
QByteArray hexAddress() const;
static QString msgNotInScope();
static QString shadowedName(const QString &name, int seen);
@@ -119,7 +121,7 @@ public:
QByteArray type; // Type for further processing
QString displayedType;// Displayed type (optional)
QByteArray variable; // Name of internal Gdb variable if created
QByteArray addr; // Displayed address
quint64 address; // Displayed address
QString framekey; // Key for type cache
QScriptValue scriptValue; // If needed...
bool hasChildren;
@@ -127,6 +129,7 @@ public:
bool valueEnabled; // Value will be greyed out or not
bool valueEditable; // Value will be editable
bool error;
QByteArray dumperFlags;
public:
int source; // Originated from dumper or symbol evaluation? (CDB only)