Re: GDB 7.11 vs. 7.12+ -- expected behaviour after posting a "continue" event?
Jonah Graham <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAPmGMvg_v0gEH6W2_nfHYOQm+D1dpVrZ15jGdAchPxibehyk5w@mail.gmail.com> |
On Sat, 15 Feb 2020 at 13:31, Adrian Oltean <[email protected]> wrote: > I have a set of python scripts that execute "continue" via gdb.post_event() at some point. What I noticed is a weird behaviour after switching to GDB 7.12+. Initially, I've been using GDB 7.11. I think this "weird behaviour" can me summarized as continue is now being run in the background. i.e. it behaves as if "continue&" had been run in the CLI instead of "continue" Adrian and I have been discussing this on CDT's dev mailing list. The assumption is that this changed related to "new-ui" as the behaviour changed between 7.11 and 7.12. I can confirm that commit a8836c9 [1] specifically as part of the new-ui change causes the behaviour change. That commit changes some of the sync/async behaviour. I tried reverting a8836c9 on top of the gdb-7.12-release tag and the continue behaviour returns to the pre-7.12 behaviour. I assume this change was an unintended side effect. @Pedro is this something that can or should be fixed/changed? Thanks, Jonah [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=a8836c9358a11055a08d11ecacc5d7c8f6d5e7a8