This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PING][PATCH] Remove stale breakpoint step-over information
- From: "Maciej W. Rozycki" <macro at wdc dot com>
- To: gdb-patches at sourceware dot org
- Cc: Pedro Alves <palves at redhat dot com>, Jim Wilson <jimw at sifive dot com>
- Date: Tue, 29 Oct 2019 21:53:08 +0000 (GMT)
- Subject: [PING][PATCH] Remove stale breakpoint step-over information
- Ironport-sdr: nosVZWcVSNsOFjcUMGeKVQZr6FIev1ZWWhTzBTcU79928qkmg0zCfJUgWVWdJPVwUg2YPQwon4 olI+5PkmBWt7ukWnqWrdlLrl2gy6+8EnEebSTMivZq7mkFTIe6P5yMtv/SqVy+LNA8UeDNUNqK EKQ6o3vo0oFA8e13zupso7C8GwsfoVeNJPR7ywqzIMeG3DE9AoKacSPp3gm/TTJnVVZ65QYKs3 7uH5puPW9I2TSwvfTrBNbCDGGbD7fqNwkMkejhoouW4+qL6YbR5MD/1uLXWzUXdsvmvy3Mz6Pt kR8=
- Ironport-sdr: +wK/kds2VunI3NUtVZln3lQX9Lhq+wV7ejOR2WwICKGWZEV4b4b6LRQ7MxSGerMUbdwjg7A8Dm 8Z4CKHSvMeEAt6cx/4DnNSv4oLG30/ZjKZFJoBFiBAc8KrGF/TuNA8RdEKVtafA8NDPL9DThae UE7uARvbeQijyRoroa2dhIGJ0Ja3sOt4a+Tox8dQQ6uEWk6D7M0WikplFLoMRqydCTP/pbiGeu +gEVwRH9rRp3piRZQpSBPEiOaW+p2jmlwcVZpiBl9b+QgaFgC/JZjAA4NOwaPusAw1o8o1ZEAQ B2QXIYQWHEDzFXEEjqkAnWBb
- Ironport-sdr: 3UyFiKsr11+Ep1tvpbGiB+jIoasBvzBvSNHttyA/uCPtUv8BYVLwN3amWIb90MskBjuBwVwSFs 0PeOoUY85I5hBejGfjCPwh866Mww+VkYnJa/IwNmhqhFzFIzRmkozZQLDnoneIvHIBKhnWSLXg AiGCRK3VoVqpGRw4syqTi4MGKhBkoDfHMcPNDhWCCDQzdotwuw1SanzSylOcVNogHBlXfsAxoW rATv2mUIXxSX0Ed703IJvFRfYE28WRJu2IjmJuxQKjhWglQt/YRymAebOZq1h0AjoSQ6Rd88QE Z/U=
- References: <alpine.LFD.2.21.1910182100030.2438@redsun52.ssa.fujisawa.hgst.com>
- Wdcironportexception: Internal
On Sat, 19 Oct 2019, Maciej W. Rozycki wrote:
> Fix an issue with the `step_over_info' structure introduced with commit
> 31e77af205cf ("PR breakpoints/7143 - Watchpoint does not trigger when
> first set"), where information stored in there is not invalidated in a
> remote debug scenario where software stepping in the all-stop mode is
> forcibly interrupted and the target connection then closed. As a result
> a subsequent target connection triggers an assertion failure on
> `ecs->event_thread->control.trap_expected' and cannot be successfully
> established, making the particular instance of GDB unusable.
Ping for:
<https://sourceware.org/ml/gdb-patches/2019-10/msg00659.html>
Maciej