On Wed, Apr 13, 2011 at 11:28 AM, Christoph Mathys <[email protected]> wrote: > Oh, I forgot: Why is it that threadname is not called if I'm attached > to a core file? All the information needed is there, the command works > if I execute it manually...
This happens because in GdbEngine::updateAllPython (pythongdbengine.cpp) executes the "wrong" command. It executes "-thread-list-ids", where it should call "-thread-info". The callback of thread-info will fall back to thread-list-ids, so it should be safe to always call -thread-info. Well, the problem is now: How can I rebuild and include a changed debugger plugin version? I need a qt 4.7 installation and I need to compile the plugin so it uses relative linking (rpath). > > And another strange thing: dumper.py and gdbmacros.py seem to be > executed a second time when attaching to a core. This is not the case That happens because loadDumpers() is called two times in case of a core file: Once in GdbEngine::startEngine (gdbengine.cpp) and then again in CoreGdbAdapter::handleTargetCore (coregdbadapter.cpp). The script file, however, is not executed again. This is most unfortunate in my case as it will overwrite my redefined threadname command again with the old version. Christoph _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
