Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
Tobias Hunger
qt-creator
Commits
da76dcc3
Commit
da76dcc3
authored
Aug 28, 2009
by
hjk
Browse files
debugger: the new pointer checks had been to aggressive. disable for now
parent
4e16b27b
Changes
1
Hide whitespace changes
Inline
Side-by-side
share/qtcreator/gdbmacros/gdbmacros.cpp
View file @
da76dcc3
...
...
@@ -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);
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment