diff options
| author | Pedro Alves <palves@redhat.com> | 2015-03-30 16:39:56 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-04-01 15:35:38 +0100 |
| commit | 6b403daae993621542c249c00ca1e6d3cfef1aa4 (patch) | |
| tree | 02d4f353b0972a35e4ba80ddae77cae75ad26c1d /gdb/testsuite/gdb.python/py-unwind.py | |
| parent | a14711808ece04167523a42f063ddb741e8ca866 (diff) | |
| download | binutils-6b403daae993621542c249c00ca1e6d3cfef1aa4.zip binutils-6b403daae993621542c249c00ca1e6d3cfef1aa4.tar.gz binutils-6b403daae993621542c249c00ca1e6d3cfef1aa4.tar.bz2 | |
infrun.c:resume: currently_stepping after clearing stepped_breakpoint
My all-stop-on-top-of-non-stop series manages to shows regressions due
to this latent bug. currently_stepping returns true if
stepped_breakpoint is set. Obviously we should clear
it before checking currently_stepping, not after.
Tested on x86_64 Fedora 20.
gdb/ChangeLog:
2015-04-01 Pedro Alves <palves@redhat.com>
* infrun.c (resume): Check currently_stepping after clearing
stepped_breakpoint, not before.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-unwind.py')
0 files changed, 0 insertions, 0 deletions