This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/18216] New: displaced step+deliver signal, while another thread also needs to step over breakpoint, crashes gdb on hardware step targets


https://sourceware.org/bugzilla/show_bug.cgi?id=18216

            Bug ID: 18216
           Summary: displaced step+deliver signal, while another thread
                    also needs to step over breakpoint, crashes gdb on
                    hardware step targets
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: palves at redhat dot com

gdb crashes on hardware step targets, if when we start resuming the target "in
proceed", there are multiple threads that needs to step over a breakpoint, and
we start a displaced set and deliver a signal at the same time (e.g.,
queue-signal), while _another_ thread also needs to step over breakpoint.

This is exact same use case that is mishandled on software single-step (see bug
18214) but it's like a funny mirror: on only happens with displaced stepping.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]