diff options
| author | David Blaikie <dblaikie@gmail.com> | 2012-12-04 21:05:36 +0000 |
|---|---|---|
| committer | David Blaikie <dblaikie@gmail.com> | 2012-12-04 21:05:36 +0000 |
| commit | 5a773bb601e782749e909c613bd53a1108abaa8d (patch) | |
| tree | 6f5fededb83f7cfbf5dd72e0010aa600acac4722 /lldb/source/Plugins/OperatingSystem/Python/OperatingSystemPython.h | |
| parent | 61bd3a1dc612af9bde0765f9f4e6c2847554d2ac (diff) | |
| download | bcm5719-llvm-5a773bb601e782749e909c613bd53a1108abaa8d.tar.gz bcm5719-llvm-5a773bb601e782749e909c613bd53a1108abaa8d.zip | |
Reapply r160148 (reverted in r163570) fixing spurious breakpoints in modern GDB
This reapplies the fix for PR13303 now with more justification. Based on my
execution of the GDB 7.5 test suite this results in:
expected passes: 16101 -> 20890 (+30%)
unexpected failures: 4826 -> 637 (-77%)
There are 23 checks that used to pass and now fail. They are all in
gdb.reverse. Investigating a few looks like they were accidentally passing
due to extra breakpoints being set by this bug. They're generally due to the
difference in end location between gcc and clang, the test suite is trying to
set breakpoints on the closing '}' that clang doesn't associate with any
instructions.
llvm-svn: 169304
Diffstat (limited to 'lldb/source/Plugins/OperatingSystem/Python/OperatingSystemPython.h')
0 files changed, 0 insertions, 0 deletions
