Summary: | GDB doesn't rollback displaced stepping state after a failure to insert hardware watchpoints | ||
---|---|---|---|
Product: | gdb | Reporter: | Luis Machado <luis.machado> |
Component: | gdb | Assignee: | Luis Machado <luis.machado> |
Status: | NEW --- | ||
Severity: | normal | CC: | brobecker, luis.machado |
Priority: | P2 | ||
Version: | HEAD | ||
Target Milestone: | --- | ||
Host: | x86_64-linux-gnu | Target: | x86_64-linux-gnu |
Build: | x86_64-linux-gnu | Last reconfirmed: |
Description
Luis Machado
2021-11-22 15:49:31 UTC
Hi Luis, IIUC, I think you set the target milestone for this PR to 12.1. As a side-effect, this is taken as indicating this bug needs to be fixed before we can release GDB 12. Was that your intention, and if yes, can you provide more details why? As discussed on gdb-patches: Removing target milestone date, to reflect the fact that this is not deemed release-blocking. I dug this up and noticed I did send a patch to the ML, but unfortunately I received no feedback on it and it went to patch limbo. :-) I'll pursue it again. https://sourceware.org/pipermail/gdb-patches/2021-June/179691.html Ah, nevermind. It was a similar issue. The one I posted was an earlier displaced-stepping-related bug as well. |