> It loads a library into the address space of the debugged > applications using either LD_PRELOAD or dlopen/LoadLibraryA > and uses gdb's 'call' function to execute code in that > library. Communication is done via two buffer areas in the > injected library, with gdb being used to write to and > read from these buffers. > > Note that this approach is pretty fragile and I intend to > replace it rather sooner than later by using gdb's new > python based scripting, at least on Linux and Windows. > Mac and Symbian will probably stay as they are as long as > there is no python-enabled gdb available for them. > > You could start coding the helpers for your custom types > in the currently existing scheme, the python code needed > for the new approach will look pretty similar, so the > porting effort will be minimal. > Thank you a lot for your answer. And Is there any inpormation about QDumper's API? At least I'm interesting about putItem, putHash, beginChildren methods and it's arguments format. Especially for "numchild", "exp" and all dumping mechanisms at all.
Also as was thinking before about dumping custom classes, It will be grade feature to build gdbmacroshelper not for every Qt build, but make opportunity to set project specific gdbhelper build with setting some defines to it to make specific dependence for every project. Thank you. _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
