Uploaded image for project: 'Qt Creator'
  1. Qt Creator
  2. QTCREATORBUG-3179

Breakpoint properties don't actually stick

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Not Evaluated Not Evaluated
    • Qt Creator 2.2.0
    • Qt Creator 2.2.0
    • Debugger
    • None

      I have set the ignore property on one of my breakpoints, and it doesn't seem to be working. It worked when I first created the breakpoint and set the ignore count, but it doesn't work on later debugging sessions, even though the property still shows correctly in the breakpoints pane and dialog. I have to re-create the breakpoint and reset the ignore count in ever debugging session for it to function as expected. I'm running the latest snapshot (7e48a3a314).

      I looked in the debugger log pane and do see the expected "ignore 2 10000" command with the output:

      &"ignore 2 10000\n"
      >~"Will ignore next 10000 crossings of breakpoint 2.\n"
      >59^done

      I note that a little later, there was a warning, in the output snippet:

      ALL COMMANDS DONE; INVOKING CALLBACK
      dNOTE: INFERIOR SETUP OK
      dState changed from InferiorSetupRequested(4) to EngineRunRequested(6).
      dQUEUE: RUN ENGINE
      dCALL: RUN ENGINE
      <61-exec-run
      &"warning: GDB: Failed to set controlling terminal: Invalid argument\n"

      >=thread-group-created,id="29185"
      sThread group 29185 created
      dTaking notice of pid 29185
      >=thread-created,id="1",group-id="29185"
      sThread 1 created
      >61^running
      dNOTE: ENGINE RUN AND INFERIOR RUN OK
      dState changed from EngineRunRequested(6) to InferiorRunRequested(9).
      dNOTE: INFERIOR RUN OK
      dState changed from InferiorRunRequested(9) to InferiorRunOk(10).
      dINFERIOR STARTED

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            hjk hjk
            bryceman Bryce Schober
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes