feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

debugger: the new pointer checks had been to aggressive. disable for now

Browse Source
This commit is contained in:
hjk
2009-08-28 16:11:28 +02:00
parent 4e16b27b6e
commit da76dcc32f
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
share/qtcreator/gdbmacros/gdbmacros.cpp
View File

@@ -275,9 +275,11 @@ static bool couldBePointer(const void *p)
{
// we assume valid pointer to be 4-aligned at least.
// So use this check only when this is guaranteed.
// FIXME: this breaks e.g. in the QString dumper...
const quintptr d = quintptr(p);
qDebug() << "CHECKING : " << p << ((d & 3) == 0 && (d > 1000 || d == 0));
return (d & 3) == 0 && (d > 1000 || d == 0);
//qDebug() << "CHECKING : " << p << ((d & 3) == 0 && (d > 1000 || d == 0));
//return (d & 3) == 0 && (d > 1000 || d == 0);
return d > 1000 || d == 0;
}
// Check memory for read access and provoke segfault if nothing else helps.
@@ -870,7 +872,7 @@ void QDumper::putHash(const char *name, QChar value)
endHash();
}
#define DUMPUNKNOWN_MESSAGE "<not in scope>"
#define DUMPUNKNOWN_MESSAGE "<not in scope*>"
static void qDumpUnknown(QDumper &d, const char *why = 0)
{
//d.putItem("iname", d.iname);