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. The inferior stopped because it triggered an exception.
Forum Updated to NodeBB v4.3 + New Features

The inferior stopped because it triggered an exception.

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

    Hi,

    I have built my application using Qt6.4.0 and MSVC2019 successfully. I am facing the runtime exception error as mentioned below-

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

    The same application is able run without any exception when I build using Qt5.12.3 and MSVC2017.

    Why am I facing different behavior with same code?
    Is any setting available in Qt Creator which could bypass the same?
    Kindly suggest.

    Thanks,

    jsulmJ 1 Reply Last reply
    0
    • P Pradson

      Hi,

      I have built my application using Qt6.4.0 and MSVC2019 successfully. I am facing the runtime exception error as mentioned below-

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

      The same application is able run without any exception when I build using Qt5.12.3 and MSVC2017.

      Why am I facing different behavior with same code?
      Is any setting available in Qt Creator which could bypass the same?
      Kindly suggest.

      Thanks,

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #2

      @Pradson said in The inferior stopped because it triggered an exception.:

      Why am I facing different behavior with same code?

      Most probably an issue in your code which does not always lead to a crash.
      But like always is such situations: run your app through debugger and check the stack trace after crash.

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      1

      • Login

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