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. Qt Creator fails to map breakpoints (sometimes)
Forum Updated to NodeBB v4.3 + New Features

Qt Creator fails to map breakpoints (sometimes)

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
qtcreator 4.1gdb
2 Posts 1 Posters 1.7k 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.
  • kshegunovK Away
    kshegunovK Away
    kshegunov
    Moderators
    wrote on last edited by
    #1

    Hello,
    I have the following setup:

    1. I have a module
    2. I have examples (applications) for that module.

    I've configured them as usual and building is working perfectly fine. However, when I put a breakpoint in the application Creator (actually gdb) fails to map the breakpoint to the proper memory location. From the debugger log I can see:

    "Error in re-setting breakpoint 1: Cannot access memory at address 0x820\n"
    "Error in re-setting breakpoint 2: Cannot access memory at address 0x820\n"
    

    after the inferior has been attached and runs:

    dINFERIOR ATTACHED AND RUNNING
    ~"Reading symbols from /home/nye/Programming/C++/qtdaemon/examples/daemon/customcontrol/customcontroller/customcontroller..."
    sReading /home/nye/Programming/C++/qtdaemon/examples/daemon/customcontrol/customcontroller/customcontroller......
    ~"done.\n"
    

    Library loading is okay, there are no other issues with the log.
    Interestingly enough, if I put a breakpoint in the module in a place I know it will be hit, there's no problem, the debugger waits at it. However before hitting the first breakpoint in the module it can't initialize for some reason the breakpoints in my applications.
    Switching to full paths for breakpoints didn't change any of said behavior.

    Any suggestions?

    Thanks in advance.
    Kind regards.

    Read and abide by the Qt Code of Conduct

    1 Reply Last reply
    0
    • kshegunovK Away
      kshegunovK Away
      kshegunov
      Moderators
      wrote on last edited by
      #2

      Apparently related to: https://bugreports.qt.io/browse/QTCREATORBUG-17254

      Read and abide by the 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