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

[REG 13->14] MinGW/GDB cannot add/remove breakpoints while running

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Not Evaluated
    • Qt Creator 14.0.2
    • Qt Creator 14.0.2, Qt Creator 15.0.0
    • Debugger
    • None
    • Windows, MSYS2, MinGW, GDB 15.1
    • 9d2281aff (14.0)

    Description

      Caused by commit 9d88da6c2b, if I add or remove a breakpoint while a 32-bit console application is running, QtC loses connection with the debugger, it considers the application as "stopped", and any attempt to continue results in a timeout after some time. Needless to say, the breakpoint doesn't break.

      Attached the relevant part of the logs. Notice that with QtC 13 the logs shows:

      >~"37 received signal SIGTRAP, Trace/breakpoint trap.\n"
      >~"[Switching to Thread 4324.0xa8b4]\n"
      >~"0x77474e21 in ntdll!DbgBreakPoint () from C:\\WINDOWS\\SysWOW64\\ntdll.dll\n"
      >*stopped,reason="signal-received",signal-name="SIGTRAP",signal-meaning="Trace/breakpoint trap",frame={addr="0x77474e21",func="ntdll!DbgBreakPoint",args=[],from="C:\\WINDOWS\\SysWOW64\\ntdll.dll",arch="i386"},thread-id="37",stopped-threads="all"
      d[GDB] NOTE: INFERIOR STOP OK
       Stopped.
      d[GDB] State changed from InferiorStopOk(10) to InferiorStopOk(10)
       [GDB] HANDLING QUEUED COMMANDS AFTER TEMPORARY STOP
      <27-break-insert  -f "\"SIPTrunkSettingsJsonModels.cpp\":30" 

      While with 14 it is:

      >~"[Thread 35260.0x755c exited with code 0]\n"
       [Thread 35260.0x755c exited with code 0]
      >=thread-exited,id="37",group-id="i1"
       Thread 37 in group i1 exited. --- token barrier ---
      d[GDB] NOTE: INFERIOR RUN REQUESTED
       Run requested...
      d[GDB] State changed from InferiorStopOk(10) to InferiorRunRequested(6)
       Running requested...
      <1949-exec-continue>=thread-created,id="38",group-id="i1"
       Thread 38 created.
      >~"[New Thread 35260.0x834c]\n"
       [New Thread 35260.0x834c]
      >=thread-created,id="39",group-id="i1"
       Thread 39 created.
      >~"[New Thread 35260.0x8760]\n"
       [New Thread 35260.0x8760]d[GDB] 1949: -exec-continue
      d[GDB] TIMED OUT WAITING FOR GDB REPLY. COMMANDS STILL IN PROGRESS: "-exec-continue" 

      Reverting 9d88da6c2b completely (it was partially reverted in 2364448f910) fixes the issue for me.

      Attachments

        1. gdb-13.txt
          5 kB
        2. gdb-14.txt
          3 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            hjk hjk
            orgads Orgad Shaneh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes