Qt Creator fails to map breakpoints (sometimes)


  • Qt Champions 2016

    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.


  • Qt Champions 2016


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.