Uploaded image for project: 'Qt Visual Studio Tools'
  1. Qt Visual Studio Tools
  2. QTVSADDINBUG-733

Plugin seems to force NDEBUG define, breaking assertions

    XMLWordPrintable

    Details

    • Platform/s:
      Windows
    • Commits:
      6cfad4728f804130730f165cd293f92c48bce70f

      Description

      Using assetions is critical for our testing. Unfortunately, Qt Vs Tools seems to disable assertions by forcing NDEBUG define for some reason - even in Debug configuration).

      Steps to replicate:

      1) Create new "Qt Console Application" project

      2) Open "main.cpp" and add " assert(false == true);" before Qt application initialization:

      3) Run the app in Debug mode - assertion is not hit

      4) Go to "assert" definition, NDEBUG seems to be defined:

       

       

       

       

       

        Attachments

        1. assert_exception.gif
          2.33 MB
          Miguel Costa
        2. assert.avi
          8.49 MB
          SeeR
        3. HelloWorld.zip
          320 kB
          SeeR
        4. image-2020-01-07-12-39-56-221.png
          11 kB
          Michael Kostukov
        5. image-2020-01-07-12-40-53-808.png
          18 kB
          Michael Kostukov
        6. image-2020-01-07-12-41-24-682.png
          12 kB
          Michael Kostukov
        7. image-2020-01-07-12-46-45-580.png
          9 kB
          Michael Kostukov
        8. image-2020-01-20-17-59-22-736.png
          50 kB
          SeeR
        9. msbuild.binlog
          365 kB
          SeeR
        10. screenshot-1.png
          78 kB
          SeeR
        11. screenshot-2.png
          55 kB
          SeeR

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTVSADDINBUG-764 Debug mode sets wrong NDEBUG flag.

          • Not Evaluated - Not yet evaluated/prioritized
          • Closed
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-81569 qmake: NDEBUG macro always added, regardless of configuration

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              Assignee:
              mecfc Miguel Costa
              Reporter:
              r0ll1ngst0ne Michael Kostukov
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes