Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. [resolved] moved source from Mac to PC, now getting debug error
Qt 6.11 is out! See what's new in the release blog

[resolved] moved source from Mac to PC, now getting debug error

Scheduled Pinned Locked Moved Installation and Deployment
3 Posts 2 Posters 2.0k 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.
  • mzimmersM Offline
    mzimmersM Offline
    mzimmers
    wrote on last edited by
    #1

    I just moved a stable source base from the Mac to a PC. It claims to build correctly, but I'm having two issues, which may or may not be related:

    I've configured for both a debug and release version. In both directories, though, it has subdirectories called "debug" and "release"...this didn't happen on the Mac, and it's making me think I did something wrong.

    When I try to start the debugger, I get the following error (many times):

    bq. (Internal error: pc 0x44 in read in psymtab, but not in symtab.)

    So...what did I do wrong?

    1 Reply Last reply
    0
    • sierdzioS Offline
      sierdzioS Offline
      sierdzio
      Moderators
      wrote on last edited by
      #2

      Ad. 1. The debug and release thing is standard on Windows. There are many topics about it on this forum, and I think the case is mentioned in qmake manual. I don't remember if there is any solution.

      Ad. 2. No clue, I'm not using Windows.

      (Z(:^

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

        OK, thanks for letting me know about the first issue.

        I'm reinstalling Virtual Studio and doing some other maintenance on this piece of junk PC I'm stuck with...maybe I can make the second issue go away. I should know within 24 hours, and will report back.

        EDIT: yeah, that made the debug problem go away; seems to be working now.

        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