forked from qt-creator/qt-creator
Debugger: Drop 'set print object on' for GDB
This does not seem to affect the code paths we are using through Python. Task-number: QTCREATORBUG-23965 Change-Id: I2e20d6d3c1937d56293e81b74c453e83a92ddc4c Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This commit is contained in:
@@ -3637,7 +3637,6 @@ void GdbEngine::setupEngine()
|
||||
//runCommand("define hookpost-stop\nprint 5\nend");
|
||||
//runCommand("define hook-call\nprint 6\nend");
|
||||
//runCommand("define hookpost-call\nprint 7\nend");
|
||||
runCommand({"set print object on"});
|
||||
//runCommand("set step-mode on"); // we can't work with that yes
|
||||
//runCommand("set exec-done-display on");
|
||||
//runCommand("set print pretty on");
|
||||
|
@@ -1532,7 +1532,6 @@ void tst_Dumpers::dumper()
|
||||
#else
|
||||
"file doit\n"
|
||||
#endif
|
||||
"set print object on\n"
|
||||
"set auto-load python-scripts off\n";
|
||||
|
||||
cmds += "python sys.path.insert(1, '" + dumperDir + "')\n"
|
||||
|
Reference in New Issue
Block a user