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 doesn't stop on breakpoints fully, due to unexpected gdb state transitions
Forum Updated to NodeBB v4.3 + New Features

Debugger doesn't stop on breakpoints fully, due to unexpected gdb state transitions

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
2 Posts 2 Posters 358 Views
  • 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.
  • S Offline
    S Offline
    StVO
    wrote on last edited by
    #1

    Im trying to debug a Qt Application with external libraries. During debug in a constructor I try get the debugger to stop on a breakpoint which partially works. Until gdb suddenly switches back into running mode while trying to fill the variables view.

    *** UNEXPECTED STATE TRANSITION: Debugger::Internal::DebuggerEngine(0x4e01a90, name = "GdbEngine") "State changed from InferiorStopOk(10) to InferiorRunOk(7)"

    >&"python theDumper.fetchVariables({\"autoderef\":1,\"context\":\"\",\"displaystringlimit\":300,\"dyntype\":1,\"expanded\":{\"inspect\":100,\"local\":100,\"return\":100,\"watch\":100},\"fancy\":1,\"formats\":{},\"nativemixed\":0,\"partialvar\":\"\",\"passexceptions\":0,\"qobjectnames\":1,\"resultvarname\":\"\",\"stringcutoff\":10000,\"timestamps\":0,\"token\":31,\"typeformats\":{},\"watchers\":[]})\n"
    
    >=thread-created,id="29",group-id="i1"
     Thread 29 erzeugt.
    >~"[New Thread 0x7fffc5ffb640 (LWP 37962)]\n"
     [New Thread 0x7fffc5ffb640 (LWP 37962)]
    >*running,thread-id="29"
    dNOTE: INFERIOR RUN OK
     Läuft.
    

    There is no crosscompiling involved and I do not experience this behavior with a minimal example.

    I use following setup (with two different qtcreator versions just as a test)
    qtcreator ( 11.0 a86356ce8a / 12.0 Rev 27055e4c39 )

    gdb GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
    gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
    g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

    Any hints how to debug this further are welcome...

    Bildschirmfoto vom 2023-12-07 16-00-48.png

    JonBJ 1 Reply Last reply
    0
    • S StVO

      Im trying to debug a Qt Application with external libraries. During debug in a constructor I try get the debugger to stop on a breakpoint which partially works. Until gdb suddenly switches back into running mode while trying to fill the variables view.

      *** UNEXPECTED STATE TRANSITION: Debugger::Internal::DebuggerEngine(0x4e01a90, name = "GdbEngine") "State changed from InferiorStopOk(10) to InferiorRunOk(7)"

      >&"python theDumper.fetchVariables({\"autoderef\":1,\"context\":\"\",\"displaystringlimit\":300,\"dyntype\":1,\"expanded\":{\"inspect\":100,\"local\":100,\"return\":100,\"watch\":100},\"fancy\":1,\"formats\":{},\"nativemixed\":0,\"partialvar\":\"\",\"passexceptions\":0,\"qobjectnames\":1,\"resultvarname\":\"\",\"stringcutoff\":10000,\"timestamps\":0,\"token\":31,\"typeformats\":{},\"watchers\":[]})\n"
      
      >=thread-created,id="29",group-id="i1"
       Thread 29 erzeugt.
      >~"[New Thread 0x7fffc5ffb640 (LWP 37962)]\n"
       [New Thread 0x7fffc5ffb640 (LWP 37962)]
      >*running,thread-id="29"
      dNOTE: INFERIOR RUN OK
       Läuft.
      

      There is no crosscompiling involved and I do not experience this behavior with a minimal example.

      I use following setup (with two different qtcreator versions just as a test)
      qtcreator ( 11.0 a86356ce8a / 12.0 Rev 27055e4c39 )

      gdb GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
      gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
      g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

      Any hints how to debug this further are welcome...

      Bildschirmfoto vom 2023-12-07 16-00-48.png

      JonBJ Offline
      JonBJ Offline
      JonB
      wrote on last edited by JonB
      #2

      @StVO
      Debugger visualizer is falling over (apparently) while trying to do something like display your local Vmb... variables. I think the empty pane to the right (Name/Wert/Typ) is your Local Variables window, can you close it/select an option not to display it? Might then let you proceed. Usual issue is something to do with debug information/code in external library. Make sure everything is right version and if possible compiled for debug.

      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