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. debugging source fail? (windows, qt6)
Forum Updated to NodeBB v4.3 + New Features

debugging source fail? (windows, qt6)

Scheduled Pinned Locked Moved Solved Qt Creator and other tools
5 Posts 3 Posters 335 Views 1 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.
  • D Offline
    D Offline
    davecotter
    wrote on last edited by
    #1

    i'm on Windows
    debugging a Qt 6.2 app

    when using an example project, debugging into source works fine.
    if i pause the app, the call stack is correct:

    good.png

    however, when using my project however (which is monumental, and very custom), call stack of Qt source is all wrong:

    bad.png

    note i have the same source path mappings for both projects:

    src.png

    what part(s) of my project config or .pro file could possibly cause these symptoms?

    thanks

    -dave

    ps: free Karaoke software goes to the person who can solve this!

    jsulmJ 1 Reply Last reply
    0
    • D Offline
      D Offline
      davecotter
      wrote on last edited by
      #5

      the solution was to pass --pdb into windeployqt. I had copied the qt libs into my exe dir, but not their corresponding pdb files.

      1 Reply Last reply
      3
      • D davecotter

        i'm on Windows
        debugging a Qt 6.2 app

        when using an example project, debugging into source works fine.
        if i pause the app, the call stack is correct:

        good.png

        however, when using my project however (which is monumental, and very custom), call stack of Qt source is all wrong:

        bad.png

        note i have the same source path mappings for both projects:

        src.png

        what part(s) of my project config or .pro file could possibly cause these symptoms?

        thanks

        -dave

        ps: free Karaoke software goes to the person who can solve this!

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

        @davecotter said in debugging source fail? (windows, qt6):

        call stack of Qt source is all wrong

        In what way?

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

        1 Reply Last reply
        0
        • D Offline
          D Offline
          davecotter
          wrote on last edited by
          #3

          did you look at the good vs. bad and compare the two?

          1 Reply Last reply
          0
          • JoeCFDJ Offline
            JoeCFDJ Offline
            JoeCFD
            wrote on last edited by
            #4

            Instead pause, call this to see any difference?
            QApplication::processEvents();

            1 Reply Last reply
            0
            • D Offline
              D Offline
              davecotter
              wrote on last edited by
              #5

              the solution was to pass --pdb into windeployqt. I had copied the qt libs into my exe dir, but not their corresponding pdb files.

              1 Reply Last reply
              3

              • Login

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