Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Some problems about qt 4.8.0 and qtCreator 2.4.1

    Tools
    4
    5
    2787
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      njuFerret last edited by

      I have compiled qt 4.8.0 and qtCreator 2.4.1 from source using mingw on several PCs.

      For the lastest mingw 4.6.1(32bit, downloaded using "mingw-get-inst-20111118" tool from www.mingw.org), Win7 sp1 x64, WinXP pro sp3 x86 and Win2003 sp2 x86 were used as the OS to compile the source of qt 4.8.0 and qtCreator 2.4.1.

      After sucessful compilation in three platforms (with deal with few errors), there are some problems when runing.

      1. designer crashes on both WinXP and Win2003, while works fine under win7 x64. ( the error dialog seems show the access violation with msvcrt.dll (version 7.0.2600.5512 on WinXP) )

      2. qtCreator works fine, except crashes when click on "options"->"disigner" tab under WinXP and Win2003.

      3. gdb shipped with mingw 4.6.1 can not work properly, in all cases breakpoint were ignored. as table 1 shows.

      !https://lh6.googleusercontent.com/8Hjm6bo4HLxDGqmB4ofx1bNr475Y8j8FdWwnbIpLUCRKRLRnhrPC12M4b2CMbUftd4SwW-RFUNDBLceCM8RI0aRgLs_Trgxqbi6B1OKH0Sju(table 1)!

      For mingw 4.4.0 bundled in old Qt IDE (2010.05) , all works fine, except the gdb, shown in Table 2.
      !https://lh4.googleusercontent.com/tIZyJRwEIk2Mj7ye3OGBndfvcvTZwH4DLeePNazTKTx_1qIGr7SWMPnsXLCQrgCX9QE5ZFolczrOHroVm_4rNJaZKtOFKrmAKW4McF8vB3ax(Table 2)!

      here are gdb version info, bundled with mingw 4.4.0 from old Qt IDE (2010.05)
      ~"GNU gdb (GDB) 7.1.0.20100329-cvs\n"
      ~"Copyright (C) 2010 Free Software Foundation, Inc.\n"
      ~"License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html\n"
      ~"This is free software: you are free to change and redistribute it.\n"
      ~"There is NO WARRANTY, to the extent permitted by law. Type "show copying"\n"
      ~"and "show warranty" for details.\n"
      ~"This GDB was configured as "i686-pc-mingw32".\n"
      ~"For bug reporting instructions, please see:\n"
      ~"http://www.gnu.org/software/gdb/bugs/.\n"

      My question is how to setup a proper IDE to make the gdb and designer work fine?

      "debug logs":http://pastebin.com/aGTzBdbT when gdb crashed (mingw 4.4.0)

      1 Reply Last reply Reply Quote 0
      • M
        mlong last edited by

        Moved to the Tools forum.

        Software Engineer
        My views and opinions do not necessarily reflect those of anyone -- living or dead, real or fictional -- in this universe or any other similar multiverse node. Void where prohibited. Your mileage may vary. Caveat emptor.

        1 Reply Last reply Reply Quote 0
        • T
          tobias.hunger last edited by

          I am sorry, but there is little anyone can do about the issue with such little information.

          Please "file a bug report":http://bugreports.qt-project.org/ against Qt (Creator takes designer from there) and include a backtrace of the crashes.

          1 Reply Last reply Reply Quote 0
          • N
            njuFerret last edited by

            the ["bug report":https://bugreports.qt-project.org/browse/QTBUG-24573] has been created.
            I am trying to submit the needed information as more as possible,
            but I am not clear where the backtrace can be found,
            and what kind information should be submitted.
            Any help will be apperatated.
            thanks

            1 Reply Last reply Reply Quote 0
            • K
              koahnig last edited by

              -Thanks for filing the bug report. When you post the link to the bug report here, others are able to vote and monitor the progress as well.-

              [Edit] Did not read careful enough and overlooked the link, which is already there :-(

              Vote the answer(s) that helped you to solve your issue(s)

              1 Reply Last reply Reply Quote 0
              • First post
                Last post