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

Debugger: Leave GDB default setting for 'set overload resolution'

Browse Source 
... and work around the pecularities on the dumper side instead.

Change-Id: I0c2703aae13dabc0f3f45efb46bd556c8741a15f
Reviewed-by: hjk <hjk121@nokiamail.com>
This commit is contained in:
hjk
2013-10-22 18:58:19 +02:00
parent 363c9c87b2
commit 4497d136ce
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/plugins/debugger/gdb/gdbengine.cpp
View File

@@ -4836,8 +4836,15 @@ void GdbEngine::startGdb(const QStringList &args)
// template <class T> T foo() { return T(0); }
// int main() { return foo<int>(); }
// (gdb) call 'int foo<int>'()
// /build/buildd/gdb-6.8/gdb/valops.c:2069: internal-error:
postCommand("set overload-resolution off");
// /build/buildd/gdb-6.8/gdb/valops.c:2069: internal-error
// This seems to be fixed, however, with 'on' it seems to _require_
// explicit casting of function pointers:
// GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu
// (gdb) p &Myns::QMetaType::typeName -> $1 = (const char *(*)(int)) 0xb7cf73b0 <Myns::QMetaType::typeName(int)>
// (gdb) p Myns::QMetaType::typeName(1024) -> 31^error,msg="Couldn't find method Myns::QMetaType::typeName"
// But we can work around on the dumper side. So let's use the default (i.e. 'on')
//postCommand("set overload-resolution off");
//postCommand(_("set demangle-style none"));
// From the docs:
// Stop means reenter debugger if this signal happens (implies print).