Qt Creator and other tools

Doxygen is recommended as a tool to develop documentation of Qt projects. qdoc is an internal tool used by Qt Project.

Nice ! Since you had a working answer, please update the thread title prepending [solved] so other forum users may know that a solution has been found :)

Hi, Please don't post the same question multiple times "Duplicate":http://qt-project.org/forums/viewthread/38849/

I made the request, thanks!

I would help a bit, if you tell us, wich OS, wich debugger,... But I think you are talking about windows. see: "":http://pic.dhe.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/wsisinst_config_winreg.html hope it helps ;-)

Thanks for the reply. I asked it on the list.

3.0.1 something. It happens on all three of my arch linux installs.

Ah that's a relief! Do you have a similar solution for empty grid layouts that are populated during runtime?

Behause the compiler do not have a skip option and would stop if a file could not be open. And we need the took to get all project files and third party libs. Std include files shall be skipped. It has to be compiler independent except preprocessor defines. But these we put into into the tool also.

Hi, Please don't post the same thread twice, one is enough "Duplicate":http://qt-project.org/forums/viewthread/38611/

Hi and welcome to devnet, You should bring this topic on the qt-creator mailing list, you'll find there Qt Creator's developers/maintainers (this forum is more user oriented)

I'm currently using gdb 7.2-50.el6 on Red Hat Enterprise Linux and don't see "Load Systems Pretty Printers" in Tools->Options->Debugger->GDB. Also, the reason that I would like to view the contents of an element in the buffer is that the if statement is actually much more complicated and contains 12 different tests for values using the 9 values surrounding the main element. It would be much easier if I could have the debugger display all of those values to make sure that the test is working correctly.

To get coverage with gcov for a shared library the following steps are necessary: Create two different output directories in subprojects code and test for the files .o, .gcno, .gcda: @lib1/code/bin/obj/ lib1/test/bin/obj/@ Create a configuration file for lcov in your home directory (linux) with the following content (for more details see man lcovrc): @ geninfo_adjust_src_path = /code/bin/obj => /code geninfo_adjust_src_path = /test/bin/obj => /test @ Build the executable. (It creates .gcno files.) Set LD_LIBRARY_PATH to the shared libraries. Run the executable. (It creates .gcda files.) Run lcov: @lcov --capture --directory path_to_lib1 --output-file coverage_all.info@ Run genhtml: @genhtml coverage_all.info -o output_path@

The standard timeout is 20 seconds. It happens that gdb takes longer than that, e.g. when reading a lot of debug info. In that case, press the "Give GDB more time" button. If it happens regularly you can increase the timeout in the debugger settings.

I can reproduce this, even with command-line gdb: (gdb) p *str.d yields $3 = {<QArrayData> = {ref = {atomic = {_q_value = 135154040 } } , size = 134905058 , alloc = 1 , capacityReserved = 0 , offset = -1073745292 , ...} Note the unrealistic 'size' and 'alloc' values. So either gdb does not read debug information properly (unlikely) or the compiler produced wrong debug info, possible due to applying some optimization without adjusting debug information (more likely, happened in the past, see e.g. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44731) There is really nothing Qt Creator can do in this case. Note also that the problem does not appear when passing the parameter as const &.