Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Debugging Qt with VS 2015 IDE - Watches on Qt containers
Forum Updated to NodeBB v4.3 + New Features

Debugging Qt with VS 2015 IDE - Watches on Qt containers

Scheduled Pinned Locked Moved Solved General and Desktop
7 Posts 2 Posters 3.3k Views 2 Watching
  • 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.
  • A Offline
    A Offline
    Asperamanca
    wrote on last edited by
    #1

    I'm testing a transition to VS 2015. As an in-between step, I still use the VS 2010 compiler, but the VS 2015 IDE.

    Now, when I debug Qt applications, watches on Qt containers no longer display the values in any readable way.

    Any ideas what I could try?

    1 Reply Last reply
    0
    • Chris KawaC Online
      Chris KawaC Online
      Chris Kawa
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Visual Studio 2010 debugger used older format of visualizations, placed in a file <VS install dir>\\Common7\Packages\Debugger\autoexp.dat. Open it in some text editor and check if Qt types are there.
      If not then install latest Qt add-in. It should update that file for you. Note that there is no add-in for VS2015 from Qt Project yet, but you want to use VS2010 toolchain so install it for that version.

      A 1 Reply Last reply
      0
      • Chris KawaC Chris Kawa

        Visual Studio 2010 debugger used older format of visualizations, placed in a file <VS install dir>\\Common7\Packages\Debugger\autoexp.dat. Open it in some text editor and check if Qt types are there.
        If not then install latest Qt add-in. It should update that file for you. Note that there is no add-in for VS2015 from Qt Project yet, but you want to use VS2010 toolchain so install it for that version.

        A Offline
        A Offline
        Asperamanca
        wrote on last edited by
        #3

        @Chris-Kawa
        Thank you for that pointer. I have VS 2010 installed as well, and there it works. VS 2010 and 2015 have separate autoexp.dat files, so the addin would likely only install to the file relevant for VS 2010.
        I have tried to manually transfer the lines to the VS 2015 autoexp file. Things like QPointF work, but things like QList dont.

        Further ideas?

        1 Reply Last reply
        0
        • Chris KawaC Online
          Chris KawaC Online
          Chris Kawa
          Lifetime Qt Champion
          wrote on last edited by
          #4

          VS2015 debugger uses .natvis files now, not autoexp.dat.
          Which debugger is used in your scenario? The one from 2010 or 2015?

          A 1 Reply Last reply
          0
          • Chris KawaC Chris Kawa

            VS2015 debugger uses .natvis files now, not autoexp.dat.
            Which debugger is used in your scenario? The one from 2010 or 2015?

            A Offline
            A Offline
            Asperamanca
            wrote on last edited by
            #5

            @Chris-Kawa
            Good question. I use "Local Windows debugger", I have to find out which one that is. Give that I installed VS 2015 after VS 2010, I assume that VS 2015 is used.

            And thanks for the pointer to .natvis file. I'll research that.

            A 1 Reply Last reply
            0
            • A Asperamanca

              @Chris-Kawa
              Good question. I use "Local Windows debugger", I have to find out which one that is. Give that I installed VS 2015 after VS 2010, I assume that VS 2015 is used.

              And thanks for the pointer to .natvis file. I'll research that.

              A Offline
              A Offline
              Asperamanca
              wrote on last edited by
              #6

              So I tried to add a .natvis file from The IDE debug helpers page. Neither of the methods specified on this page did the trick, so I assume the VS 2012 natvis file does not work properly on VS 2015.

              Guess I'll have to revert to VS 2010 for the time being. Thanks for your help!

              1 Reply Last reply
              0
              • A Offline
                A Offline
                Asperamanca
                wrote on last edited by
                #7

                Solution: I added a Qt6 natvis file (which is added by the extension "Qt package" anyway), but had no .natvis file for debugging Qt5 containers.

                1 Reply Last reply
                0

                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved