Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. debugger start issues (Creator)
Forum Updated to NodeBB v4.3 + New Features

debugger start issues (Creator)

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
7 Posts 4 Posters 1.2k 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.
  • mzimmersM Offline
    mzimmersM Offline
    mzimmers
    wrote on last edited by
    #1

    Hi -

    Recently my app began balking at debug startup. Not every time, but maybe about half the time. I get a blank UI and the revolving blue circle (I'm on Windows 10). I have to stop it with Task Manager and try again.

    Does anyone else encounter this? Is there possibly some rookie mistake I'm making here, like forgetting some startup command or anything?

    jsulmJ 1 Reply Last reply
    0
    • mzimmersM mzimmers

      Hi -

      Recently my app began balking at debug startup. Not every time, but maybe about half the time. I get a blank UI and the revolving blue circle (I'm on Windows 10). I have to stop it with Task Manager and try again.

      Does anyone else encounter this? Is there possibly some rookie mistake I'm making here, like forgetting some startup command or anything?

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

      @mzimmers Could be your anti-virus blocking "suspicious" activities :-)
      If you use one try to disable it temporarily.

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

      1 Reply Last reply
      2
      • mzimmersM Offline
        mzimmersM Offline
        mzimmers
        wrote on last edited by
        #3

        Interesting idea. The problem seems to come and go in bursts, though, as though dependent upon some magic mystery variable that I've left uninitialized.

        It also just started a week or two ago, and I've had ESET for almost a year now.

        K aha_1980A 2 Replies Last reply
        0
        • mzimmersM mzimmers

          Interesting idea. The problem seems to come and go in bursts, though, as though dependent upon some magic mystery variable that I've left uninitialized.

          It also just started a week or two ago, and I've had ESET for almost a year now.

          K Offline
          K Offline
          koahnig
          wrote on last edited by
          #4

          @mzimmers

          Although I would agree with @jsulm to check for an AV encounter, it is not exactly what I would expect.

          I am windows 10 with bitdefender as AV checker. The behaviour would be different than what you describe. With bitdefender the app may start once and is suddenly vanishing. Also the executable is not found anymore, since it is shifted somewhere then.

          However, ESET might have a different strategy.

          Vote the answer(s) that helped you to solve your issue(s)

          1 Reply Last reply
          0
          • mzimmersM mzimmers

            Interesting idea. The problem seems to come and go in bursts, though, as though dependent upon some magic mystery variable that I've left uninitialized.

            It also just started a week or two ago, and I've had ESET for almost a year now.

            aha_1980A Offline
            aha_1980A Offline
            aha_1980
            Lifetime Qt Champion
            wrote on last edited by
            #5

            @mzimmers Please attach the debugger log (Windows > Views > Debugger log) for a failing case here. That may give some more insight.

            Qt has to stay free or it will die.

            1 Reply Last reply
            0
            • mzimmersM Offline
              mzimmersM Offline
              mzimmers
              wrote on last edited by
              #6

              copy of the debugger log on jumpshare

              1 Reply Last reply
              0
              • aha_1980A Offline
                aha_1980A Offline
                aha_1980
                Lifetime Qt Champion
                wrote on last edited by aha_1980
                #7

                Hi @mzimmers,

                there is not much I can see from the log, only a few lines:

                ~"error return ../../../../src/gdb-7.10.1/gdb/windows-nat.c:1283 was 5\n"

                which I cannot really interpret.

                Are you using the MinGW compiler? is GDB 7.10.1 the correct one?

                I've just one more hint for you: Avoid project directories with spaces and other non-ASCII characters within, they always leads to problems - sooner or later. I don't think that's the cause for your current problem, but you could try anyway.

                Qt has to stay free or it will die.

                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