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. QT 5.14.1 Debugger broken after MSVC 2017 update
Forum Updated to NodeBB v4.3 + New Features

QT 5.14.1 Debugger broken after MSVC 2017 update

Scheduled Pinned Locked Moved Unsolved General and Desktop
2 Posts 1 Posters 178 Views
  • 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.
  • J Offline
    J Offline
    jabroni
    wrote on last edited by
    #1

    After a year of working fine, I went to debug my program today and for the first time was greeted with the following error with the program stopping in some disassembler code:

    "The inferior stopped because it triggered an exception. 
    Stopped in thread 0 by: Exception at 0x77bb1f5f, code: 0xc0000005: read access violation at: 0xffffffffbaadf00c, flags=0x0, (first chance)."
    

    My code is simplified to the following:

    class DeviceChooser : public QMainWindow
    {
        Q_OBJECT
    
    public:
        explicit DeviceChooser(QWidget *parent = 0);
        ~DeviceChooser();
    }
    
    int main(int argc, char *argv[])
    {
        QApplication a(argc, argv);
    
        a.setApplicationName(APP_NAME);
        a.setApplicationVersion(APP_VERSION);
        a.setOrganizationName(APP_ORGANISATION_NAME);
    
        a.setWindowIcon(icon);
    
        return startApplicationNormal(a);
    }
    
    int    startApplicationNormal(QApplication &a)
    {
        DeviceChooser w;
    
        QObject::connect(&a, SIGNAL(aboutToQuit()), &w, SLOT(applicationClosing()) );
    
        w.show();   // <-- if i step over this, the error appears
        return a.exec();
    }
    

    I'm not sure really why this is happening. I've reinistalled my environment and my compilers, and even uninstalled and reinstalled visual studio build tools that I was previously using with the same result. I have also tried different compiler configurations in my build settings but no luck.

    What's odd is that if I press "run" after the exception is caught, the program will run as expected as if nothing happened. So I can run the program, but my debugger appears to be almost broken. Tracking variables, I am unable to see their values on breakpoints (cannot see contents of structs etc).

    I am using QT 5.14.1 with qwt 6.1.3.

    The stack trace through the disassembler (program stops on second line):

    0x7769448b   <+   27>        mov     eax,dword ptr [ebp-4]
    0x77bb1f5f   <+  127>        cmp     word ptr [eax],dx
    

    The only difference I can see in my configuration is that the MSVC compiler updated from 15.9.28307.2094 to 15.9.34601.69.

    J 1 Reply Last reply
    0
    • J jabroni

      After a year of working fine, I went to debug my program today and for the first time was greeted with the following error with the program stopping in some disassembler code:

      "The inferior stopped because it triggered an exception. 
      Stopped in thread 0 by: Exception at 0x77bb1f5f, code: 0xc0000005: read access violation at: 0xffffffffbaadf00c, flags=0x0, (first chance)."
      

      My code is simplified to the following:

      class DeviceChooser : public QMainWindow
      {
          Q_OBJECT
      
      public:
          explicit DeviceChooser(QWidget *parent = 0);
          ~DeviceChooser();
      }
      
      int main(int argc, char *argv[])
      {
          QApplication a(argc, argv);
      
          a.setApplicationName(APP_NAME);
          a.setApplicationVersion(APP_VERSION);
          a.setOrganizationName(APP_ORGANISATION_NAME);
      
          a.setWindowIcon(icon);
      
          return startApplicationNormal(a);
      }
      
      int    startApplicationNormal(QApplication &a)
      {
          DeviceChooser w;
      
          QObject::connect(&a, SIGNAL(aboutToQuit()), &w, SLOT(applicationClosing()) );
      
          w.show();   // <-- if i step over this, the error appears
          return a.exec();
      }
      

      I'm not sure really why this is happening. I've reinistalled my environment and my compilers, and even uninstalled and reinstalled visual studio build tools that I was previously using with the same result. I have also tried different compiler configurations in my build settings but no luck.

      What's odd is that if I press "run" after the exception is caught, the program will run as expected as if nothing happened. So I can run the program, but my debugger appears to be almost broken. Tracking variables, I am unable to see their values on breakpoints (cannot see contents of structs etc).

      I am using QT 5.14.1 with qwt 6.1.3.

      The stack trace through the disassembler (program stops on second line):

      0x7769448b   <+   27>        mov     eax,dword ptr [ebp-4]
      0x77bb1f5f   <+  127>        cmp     word ptr [eax],dx
      

      The only difference I can see in my configuration is that the MSVC compiler updated from 15.9.28307.2094 to 15.9.34601.69.

      J Offline
      J Offline
      jabroni
      wrote on last edited by
      #2

      @jabroni I should also add that I've omitted that warning that appears on launch, and instead once w.show() is called, the program stops in the disassembler code section.

      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