Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. General talk
  3. Qt 6
  4. :-1: error: Debugger encountered an exception: Exception at 0x7ff9f6e2fabc, code: 0x40080201: , flags=0x80 (first chance)
Forum Updated to NodeBB v4.3 + New Features

:-1: error: Debugger encountered an exception: Exception at 0x7ff9f6e2fabc, code: 0x40080201: , flags=0x80 (first chance)

Scheduled Pinned Locked Moved Unsolved Qt 6
5 Posts 3 Posters 917 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
    JuFu
    wrote on last edited by
    #1

    My project had this problem when compling,

    jsulmJ JonBJ 2 Replies Last reply
    0
    • J JuFu

      My project had this problem when compling,

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

      @JuFu Please post the actual error and the stack trace after the crash.
      This looks like a crash while debugging, not compiling.

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

      1 Reply Last reply
      0
      • J JuFu

        My project had this problem when compling,

        JonBJ Offline
        JonBJ Offline
        JonB
        wrote on last edited by
        #3

        @JuFu
        This is a "first chance" exception, a Windows/MSVC thing. Although you see that error does anything actually go wrong or is all well?

        J 1 Reply Last reply
        0
        • JonBJ JonB

          @JuFu
          This is a "first chance" exception, a Windows/MSVC thing. Although you see that error does anything actually go wrong or is all well?

          J Offline
          J Offline
          JuFu
          wrote on last edited by JuFu
          #4

          @JonB,@jsulm, It is an error when compiling, but it can run, and it will crash in some cases, and the crash message will display an error similar to that when compiling, but the stack situation is not visible

          JonBJ 1 Reply Last reply
          0
          • J JuFu

            @JonB,@jsulm, It is an error when compiling, but it can run, and it will crash in some cases, and the crash message will display an error similar to that when compiling, but the stack situation is not visible

            JonBJ Offline
            JonBJ Offline
            JonB
            wrote on last edited by
            #5

            @JuFu
            I do not believe that a "crash" error when running your program can be anything like or have any relation to a "crash" from a compiler. They are two totally different issues.
            I do not believe you cannot obtain a "stack trace" if your program crashes at runtime. Try running it from inside a debugger.

            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