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

debugger: use & in "p (char*)&qDumpOutBuffer". This improves the

Browse Source 
situation in release builds a bit as we get at least a list of
(afterwards failing) dumpers.
This commit is contained in:
hjk
2009-04-17 13:58:49 +02:00
parent 412a4b027d
commit 01284f2160
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/plugins/debugger/gdbengine.cpp
View File

@@ -3194,7 +3194,7 @@ void GdbEngine::runDebuggingHelper(const WatchData &data0, bool dumpChildren)
.arg(m_pendingRequests + 1), 10000);
// retrieve response
sendSynchronizedCommand("p (char*)qDumpOutBuffer", WatchDebuggingHelperValue2, var);
sendSynchronizedCommand("p (char*)&qDumpOutBuffer", WatchDebuggingHelperValue2, var);
}
void GdbEngine::createGdbVariable(const WatchData &data)
@@ -4208,14 +4208,14 @@ void GdbEngine::tryLoadDebuggingHelpers()
#endif
// retreive list of dumpable classes
sendCommand("call qDumpObjectData440(1,%1+1,0,0,0,0,0,0)");
sendCommand("p (char*)qDumpOutBuffer", GdbQueryDebuggingHelper);
sendCommand("p (char*)&qDumpOutBuffer", GdbQueryDebuggingHelper);
}
void GdbEngine::recheckDebuggingHelperAvailability()
{
// retreive list of dumpable classes
sendCommand("call qDumpObjectData440(1,%1+1,0,0,0,0,0,0)");
sendCommand("p (char*)qDumpOutBuffer", GdbQueryDebuggingHelper);
sendCommand("p (char*)&qDumpOutBuffer", GdbQueryDebuggingHelper);
}
IDebuggerEngine *createGdbEngine(DebuggerManager *parent, QList<Core::IOptionsPage*> *opts)